Closed Bug 1717887 Opened 3 years ago Closed 3 years ago

Add background hang reporting for "Renderer" thread

Categories

(Core :: Graphics: WebRender, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
92 Branch
Tracking Status
firefox92 --- fixed

People

(Reporter: jrmuizel, Assigned: bradwerth)

Details

Attachments

(3 files)

Well it looks like we could technically plumb this together on top of the Chromium thread stuff it seems like we'd have to reach into the guts to figure out when the thread is going to wait. It's probably better to just switch to using an nsThread like the Compositor thread.

I'll take this on.

Assignee: nobody → bwerth
Severity: -- → S3
Priority: -- → P4

Instead of warning against callers directly accessing the thread message loop,
actuually prevent them from doing so. This is also a preliminary step to
changing the type of the internally-created thread, which will no longer
directly expose its message loop.

FWIW, I had this WIP before going on leave. It looks like you're doing it more cleanly.

The background hang monitor uses the same timing thresholds as the one used by
the compositor thread, for similar reasons.

Depends on D119562

Pushed by bwerth@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8614cd64ce97
Part 1: Abstract RenderThread task pushing, and make it private. r=gfx-reviewers,jrmuizel
https://hg.mozilla.org/integration/autoland/rev/8da7074793a3
Part 2: Make RenderThread backed by nsIThread, with a hang monitor. r=gfx-reviewers,jrmuizel
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: