Chrome limits setTimeout() to 1 call per second when the tab loses focus. I haven't gotten a chance to look at the code, but if three.js uses requestAnimationFr

Chrome limits setTimeout() to 1 call per second when the tab loses focus. I haven't gotten a chance to look at the code, but if three.js uses requestAnimationFrame and the physics uses setTimeout, things might get out of sync.