Bug 133247 - DisplayRefreshMonitorManager can only handle one kind of DisplayRefreshMonitor per PlatformDisplayID
Summary: DisplayRefreshMonitorManager can only handle one kind of DisplayRefreshMonito...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-23 18:34 PDT by Tim Horton
Modified: 2014-05-23 18:34 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Horton 2014-05-23 18:34:40 PDT 
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.