In Chrome too, it is due to the JS engine working slowly when the focus is not on the tab anymore. To get around that issue he needs to wrap the setInterval function in a Web Worker, so the thread runs independently of the tab.