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: Severity: None
Keywords: Cc:


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():

Performance counter value may unexpectedly leap forward:;EN-US;Q274323&

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

PS Before Valik tears me a new one: I'm sorry for opening a new ticket.

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.

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.