Chromium doesn't seem to handle backwards time jumps very well, but the behavior is especially strange on Windows. Steps to reproduce on Windows: 1. Open this page, observe normal behavior. 2. Move the Windows system clock back 2 minutes. 3. Observe: For the next 40-50 seconds, timers fire in 1 second. Then, a timer is (surprise) delayed by 1-3 minutes. After it fires, timers resume firing in 1 second. I saw this behavior on: Chrome 4.0.249.89 (38071) on Windows Server 2008 R2 on bare metal, Core 2 Q6600 Chrome 4.1.249.1025 beta (40600) on XP SP3 32-bit on VMWare Workstation 7.0.1 Chrome 5.0.342.2 dev on XP SP2 64-bit on VMWare Workstation 7.0.1 Steps to reproduce on Ubuntu or OS X: (1) and (2) same as above; 3. Observe: A timer is delayed by 2 minutes. After it fires, timers resume firing in 1 second. I saw this behavior on: Chrome 5.0.307.11 beta on Ubuntu 9.10 32-bit on VMWare Workstation 7.0.1 Chrome 5.0.307.11 beta on Mac OS X 10.6.2 More behavior observed on Windows: IE8, Firefox 3.6, Firefox 2.0.0.20, and Opera 10.50 appear to schedule timers with a monotonic clock, and do not attempt to conceal a backwards time jump when calling Date.getTime(). Safari 4.0.4 and 3.1.2 on Windows have strange behavior and might be correcting timers after clock jumps.