Do not aggressively throttle DOM timers until they've reached their max nesting level. This is what's causing Google Maps to use 100% CPU usage in background tabs for several minutes.
<rdar://problem/29808005>
Created attachment 302354 [details] Patch
Comment on attachment 302354 [details] Patch Is there a way to test this?
(In reply to comment #3) > Comment on attachment 302354 [details] > Patch > > Is there a way to test this? Maybe. I'll look into it tomorrow.
Created attachment 302405 [details] Patch
Comment on attachment 302405 [details] Patch Attachment 302405 [details] did not pass ios-sim-ews (ios-simulator-wk2): Output: http://webkit-queues.webkit.org/results/3173399 New failing tests: fast/dom/timer-throttling-hidden-page.html
Created attachment 302409 [details] Archive of layout-test-results from ews121 for ios-simulator-wk2 The attached test failures were seen while running run-webkit-tests on the ios-sim-ews. Bot: ews121 Port: ios-simulator-wk2 Platform: Mac OS X 10.11.6
Created attachment 302411 [details] Patch
Comment on attachment 302411 [details] Patch Clearing flags on attachment: 302411 Committed r212845: <http://trac.webkit.org/changeset/212845>
All reviewed patches have been landed. Closing bug.