[Webkit-unassigned] [Bug 131697] New: Move DOM timer throttling out of the page throttler

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 15 14:50:17 PDT 2014


           Summary: Move DOM timer throttling out of the page throttler
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Keywords: InRadar
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: slewis at apple.com
                CC: barraclough at apple.com
        Depends on: 131696

Stephanie Lewis <slewis at apple.com> changed:

           What    |Removed                     |Added
 Attachment #229405|                            |review?
               Flag|                            |

Created an attachment (id=229405)
 --> (https://bugs.webkit.org/attachment.cgi?id=229405&action=review)

DOM timer throttling is currently part of the page throttler which uses per process state and per page state to determine when to throttle.  This led us to being overly conservative when turning DOM throttling off.  It should only respond to view state changes.

Additionally since creating extra Page Throttlers for WebKit1 views and SVG images caused bugs in tracking state we'll reserve the Page Throttler for WebKit2 views.  To avoid regressing we should move DOM timer throttling back to the page.

<rdar://problem/16473004> Throttling DOM timers should be per-page, not per-process

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list