Opened 15 years ago
Closed 15 years ago
#1085 closed Bug (No Bug)
General timer descrepancies
| Reported by: | Zoster | Owned by: | |
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.3.0.0 | Severity: | None |
| Keywords: | Cc: |
Description
In continuation of #1082:
Well I certainly believe that it works for you but the problem seems to be suprisingly wide spread. Please see:
Beware of QueryPerformanceCounter():
http://www.virtualdub.org/blog/pivot/entry.php?id=106
Performance counter value may unexpectedly leap forward:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q274323&
http://www.mindcontrol.org/~hplus/pc-timers.html
Not sure what you guys can do about it but I think it should be noted in the help file that those variances might occur. I'm using the @timemacros as a workaround for now.
Attachments (0)
Change History (4)
comment:1 Changed 15 years ago by Zoster
comment:2 Changed 15 years ago by Valik
Sorry doesn't put all this crap into the old ticket where it belongs.
comment:3 Changed 15 years ago by Jpm
Not sure to understand what can be done in this subject.
Do we need to support HW which does not report the high precision counters with correct value?
Do we need to force running the AutoIt process on only one processor to have the high precision counter better in multiprocessor system?
comment:4 Changed 15 years ago by Valik
- Resolution set to No Bug
- Status changed from new to closed
Microsoft lists 9 chipsets that are affected. I really don't think we need to document a problem that's due to a hardware defect on so few chipsets.
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
PS Before Valik tears me a new one: I'm sorry for opening a new ticket.