It seems like there has been a change to some recent version of Chrome and Firefox*, and now Javascript execution seems to be different when the tab it is being run in is not the currently focused one.
When I run my Javascript unit tests, they normally take about 20 seconds to complete but now, when the tab is unfocused, it takes upwards of 2000 seconds. What is strange though, is that the run times for each individual test are not affected (most are still < 10ms). The test runner I’m using adds a setTimeout(0) between running each test so that the browser doesn’t lock up while executing, and so that seems the likely culprit.
Is there a way to tell the Javascript engine not to “deprioritise” that tab though? It’s nice to be able to run my tests in the background without having to watch myself…
*sorry, I don’t really care enough to try installing old versions to find when this started happening. At the very least, it’s happening now on Firefox 5.0 and Chrome 12.
setTimeoutandsetIntervalhave been throttled to a minimum of 1000ms in unfocused tabs. Here is the Bugzilla report that mentions it. And here is the similar Chromium bug report. I believe this is the case in Firefox 5 and in Chrome since version 11.According to MDN:
As for getting around this restriction, you could try the technique discussed in this article, but I haven’t had a change to try it myself yet.