Use a single threaded webview compositor

Bug #1426153 reported by Chris Coulson
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Chris Coulson

Bug Description

The webview compositor currently runs on a separate thread - it's like this because at one stage it looked like Google were going to remove the single threaded mode. However, they seem to have settled on a single-threaded browser compositor for now.

A threaded webview compositor has always been unnecessary in Oxide for a few reasons:
- It doesn't handle any animations, so there are no cases where it needs to remain responsive if the main thread is blocked.
- It only contains a single visible layer - the delegated frame layer. Updating this involves the main thread anyway.
- Unlike the renderer main thread which runs arbitrary script, what runs on the browser main thread is controlled by the embedder and predictable. The browser main thread should never be busy enough to block the compositor.
- It adds unnecessary complexity.
- It introduces additional thread hops.

Changed in oxide:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I reckon this is going to be needed to fix bug 1549459

Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
importance: High → Critical
milestone: none → branch-1.14
Changed in oxide:
status: Triaged → In Progress
Changed in oxide:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers