✳flâneur — a map of the web's best reading

STRML: Chrome 56 Will Aggressively Throttle Background Tabs

blog.strml.net · 2,972 words · saved by 1 readers

did you just do a setInterval with printing current time ? If so the 'budget' mechanism is not really working is it ? otherwise a simple lower priority / less cpu based on device capabilities etc would be acceptable to me No - this was a setInterval running at the same time as the regular work my existing production application does. So it's a good representation of what timers on a typical SPA might be throttled to. RIP cookie-clicker and cookie-clicker-alikes. And that loligater game. You just killed my productivity for today Damn Internet! I am worry about apps like soundcloud or spotify (web versions) that will die and stop playing or making big pauses between songs. Will make sense to show a pop up (requested manually by the app) to ask for "run on background" permission? That shouldn't be a problem as apparently "tabs with audio are always considered foregrounded". Source: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/-dmrNAFHd-4/discussion And there's your wo

STRML: Chrome 56 Will Aggressively Throttle Background Tabs Monday, January 23, 2017 Chrome 56 Will Aggressively Throttle Background Tabs [Jan 26, 7:25am]: Google has responded to this article and the plans for throttling: Unfortunately, our current implementation throttles WebSockets. Because of this we ARE NOT SHIPPING this intervention in M56. The current plan is to disable time-budget background timer throttling for the pages with active connection (websocket, webrtc and server-sent events) and to ship in M57 (subject to further feedback). We will keep you updated with the progress. ------

Explore this link on the map →

related reading