1646799 - setInterval(..., 0) is not clamped, unlike setTimeout(..., 0)

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect, P3)

Description

[Markus Stange [:mstange]]

Attachment: testcase

In this testcase, Firefox reports one call every 0.009ms, and Chrome reports one call every ~4ms.

This is causing excess resource usage on misbehaving websites such as https://www.gamesradar.com/ .

Comment 1

[Danial Horton]

I'm not sure where that See also fits in, the behavior is occuring only in the active tab?

Comment 2

[Mirko Brodesser (:mbrodesser-Igalia)]

(In reply to Danial Horton from comment #1)

I'm not sure where that See also fits in, the behavior is occuring only in the active tab?

The ticket linked under "See Also"? It's also about throttling of the same method, therefore it could be relevant.

Comment 3

[Danial Horton]

Some of these sites along with the quantcast script that causes this, are also loading a widget that also causes it, from https://widgets.future-fie.co.uk/

Comment 4

[[e-mail]]

Note that on https://www.gamesradar.com/ and others, the offending setInterval() calls look like:

setInterval("function() { [native code] }", NaN);

Comment 5

[Markus Stange [:mstange]]

Another case: https://www.tvtechnology.com/news/whats-the-difference-between-5994fps-and-60fps

Comment 6

[Olli Pettay [:smaug][[e-mail]]]

Attachment: Bug 1646799 - setInterval(..., 0) is not clamped, unlike setTimeout(..., 0), r=peterv

Comment 7

[Olli Pettay [:smaug][[e-mail]]]

hmm, I lost the link to my tryserver push.
Doing it again: https://treeherder.mozilla.org/#/jobs?repo=try&revision=8d2573cf95c064aefc6015a735fd41425266d93f
And apparently I had left a tiny bug in the test.

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/1df40ae8828d
setInterval(..., 0) is not clamped, unlike setTimeout(..., 0), r=peterv

Comment 9

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/1df40ae8828d