You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can the problem happen:
1. current time = 0xFFFF0000
2. timer should expire at 0xFFFFFFF8
3. the counter expires at 0xFFFFFFF8, but by the time the software is
reading the current time, it has rolled over to 0x00000002 and when it
compare that value to the timer expiration date, it concludes it has not
yet expired
The goal is not to miss and timer in the list. Unfortunately this scenario
can happen.
Original issue reported on code.google.com by [email protected] on 11 Jan 2010 at 2:12
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 11 Jan 2010 at 2:12The text was updated successfully, but these errors were encountered: