[SystemHalted]

:/

http://blog.strml.net/2017/01/chrome-56-now-aggressively-throttles.html

Chrome 56 introduces a commendable optimization to throttle background tabs' timers.

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.

Worse yet, the heuristic is based on local CPU time; faster clients may have no issue and face no throttling, but slower devices often will, causing cascading processing and notification delays.

#chrome