(In reply to Andrew Overholt [:overholt] from comment #3) > Thanks for the regression range! It's quite a lot of stuff but my naive look at the pushes makes me think maybe those from bug 1363829 could be related (especially given your comment 2). I agree with that assessment. The game relies on setTimeout for precise frame scheduling. This is not a good idea in general, because by default, the timer resolution on Windows is really bad. However, if websites keep doing it, and if other browsers work fine, we'll have to do something about it. I think there are two potential reasons why bug 1363829 may have made this worse: 1. It might have stopped us from telling Windows to enable higher-resolution timers, or 2. It might have resulted in worse setTimeout accuracy in scenarios where timer resolution is already bad to begin with.
Bug 1683560 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Andrew Overholt [:overholt] from comment #3) > Thanks for the regression range! It's quite a lot of stuff but my naive look at the pushes makes me think maybe those from bug 1363829 could be related (especially given your comment 2). I agree with that assessment. The game relies on setTimeout / setInterval for precise frame scheduling. This is not a good idea in general, because by default, the timer resolution on Windows is really bad. However, if websites keep doing it, and if other browsers work fine, we'll have to do something about it. I think there are two potential reasons why bug 1363829 may have made this worse: 1. It might have stopped us from telling Windows to enable higher-resolution timers, or 2. It might have resulted in worse setTimeout accuracy in scenarios where timer resolution is already bad to begin with.