In bug 1342854 I introduced a pref to control how many timer callbacks can be coalesced into a single runnable. The code, however, allows "<prev value> + 1" callbacks to be coalesced. Its not a critical problem, but we should fix it.
Created attachment 8842888 [details] [diff] [review] Don't allow an extra timer callback beyond configured pref value. r=smaug I realized yesterday that I implemented the pref based limit in TimeoutManager::RunTimeout() slightly wrong. I need to update the count before checking against the limit. As the code is now we always allow one additional timer callback to run. Since this effectively lowers the limit by one I re-tested foofighters.com. I couldn't measure a noticeable difference with the new limit. So I propose we just leave the default 5 and we will no actually execute 5 instead of 6.
Attachment #8842888 - Flags: review?(bugs)
I'd like to uplift this to FF53, but not worth uplifting to FF52.
status-firefox51: --- → unaffected
status-firefox52: --- → wontfix
status-firefox53: --- → affected
status-firefox54: --- → affected
status-firefox-esr45: --- → unaffected
status-firefox-esr52: --- → wontfix
Comment on attachment 8842888 [details] [diff] [review] Don't allow an extra timer callback beyond configured pref value. r=smaug oops, sorry, I should have noticed. numTimersToRun >= gTargetMaxConsecutiveCallbacks uses indeed >= and not >
Attachment #8842888 - Flags: review?(bugs) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/370ba5872bf6 Don't allow an extra timer callback beyond configured pref value. r=smaug
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
status-firefox54: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.