Comment #11 on issue 22508 by [email protected]: Tab doesn't update until context menu displayed after waking from sleep http://code.google.com/p/chromium/issues/detail?id=22508
I spent some time debugging this bug this evening. After collecting a bunch of data, then chatting with TVL and reading some CF source, I think I figured out what's going on. CFRunLoopTimers seem to be implemented in terms of CFAbsoluteTime (delta from 2001-01-01 00:00:00.0Z) which would imply that they fire on that schedule, but in fact, under the covers, they're using kernel ticks (as in mach_absolute_time) which are suspended while the system is sleeping. This means that if you put your computer to sleep for 9 seconds and then wake it up, your pending timer will be delayed by 9 seconds. The solution will be to listen for a wake-up notification and reset the timer using the last-known next-fire time. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
