[Webkit-unassigned] [Bug 133247] New: DisplayRefreshMonitorManager can only handle one kind of DisplayRefreshMonitor per PlatformDisplayID

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 23 18:34:17 PDT 2014


https://bugs.webkit.org/show_bug.cgi?id=133247

           Summary: DisplayRefreshMonitorManager can only handle one kind
                    of DisplayRefreshMonitor per PlatformDisplayID
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: thorton at apple.com
                CC: simon.fraser at apple.com, dino at apple.com


After bug 132794, we have different kinds of DisplayRefreshMonitors between e.g. UI-side compositing and traditional compositing.

DisplayRefreshMonitorManager is a singleton and only handles one DisplayRefreshMonitor per PlatformDisplayID.
Therefore, if you had e.g. a UI Side compositing view and a traditional compositing view on Mac, both sharing a display, and both views tried to use rAF (or whatever), one of them would lose and get the wrong kind of Monitor. This could lead to performance problems or other brokenness.

However! This is currently not a supported configuration by any means so the problem is currently purely theoretical.

-- 
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