4ec676871d9 "[scheduler] Change ThreadLoadTracker to use only recent data" revision was landed on October 6th and contains UMA metric fix which we need. Please merge it into M55.
I would also like to understand how this could be affecting working code. From the one sentence description I cannot really see what code will be throttled by Chrome and when under what circumstances. Is there a link to some specification or discussion that I am not seeing? This sounds a bit like the recent setTimeout "improvements" so developers need to start working on workarounds and be prepared to be confronted with new bug reports for their existing applications.
Does this mean that if you focus another tab that the original tabs can be throttled up to 99%?
https://www.chromestatus.com/features/6172836527865856 contains some links with more detailed information about this.
TL;DR: Background timers (setTimeout & setInterval) will be throttled. Throttling will become active when a tab is backgrounded (you focus a new tab and old tab becomes completely invisible). We're also interested in use cases when this approach breaks something.
Comment 1 by bugdroid1@chromium.org
, Aug 23 2016