Bug 1645528 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Currently, WaylandVsyncSource is only used in the main process, for refresh drivers and composition scheduling. Refresh drivers in content processes fall back to a synthetic 60Hz source.

An IPC mechanism already exists to guide vsync to content processes, but it assumes a global vsync source is available.

Instead, a separate IPC mechanism should be used to connect the nsRefreshDriver with its associated root widget.
Revision 1 by
on 
Currently, WaylandVsyncSource is only used in the main process, for refresh drivers and composition scheduling. Refresh drivers in content processes fall back to a synthetic 60Hz source.

An IPC mechanism already exists to guide vsync to content processes, but it assumes a global vsync source is available.

Instead, a separate IPC mechanism should be used to connect the nsRefreshDriver with its associated root widget. If we move nsRefreshDrivers between native widgets, we also need to make sure to relocate them.

Back to Bug 1645528 Comment 0