If you rely on JavaScript’s setInterval() in your code, chances are you’re going to be in a world of pain in future Chrome releases.
When idle, your application’s timers may be delayed for minutes. Aside from terrible hacks like playing zero-volume sounds, you have no control over this. Avoiding expensive CPU work is not a panacea; that some applications must do significant work in the background, including syncing data, reading delta streams, and massaging said data to determine whether or not to alert the user.
Source: STRML: Chrome 56 Will Aggressively Throttle Background Tabs