Open Bug 1644883 Opened 5 years ago Updated 11 months ago

Compositor thread isn't shut down properly

Categories

(Core :: Graphics, defect)

defect

Tracking

()

People

(Reporter: jesup, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

The Compositor thread isn't shut down when we drop the CompositorThreadHolder, which means nsThreadManager has to clean it up later.

See Bug 1644254 which is relevant to this.

The issue is that the APZ and Canvas (and I think the VR manager) are dispatches task on the compositor thread after CompositorThreadHolder::Shutdown() has been called.

It didn't cause problem earlier because the compositor thread was a google's MessageLoop.

So if we do shutdown the thread in here, or in the CompositorThreadHolder singleton destructor ; those tasks dispatched would never run.
I don't know if that is a problem or not; but my guess leaking that thread isn't something to be worried about

See Also: → 1644254

The severity field is not set for this bug.
:jbonisteel, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jbonisteel)
Severity: -- → S3
Flags: needinfo?(jbonisteel)
Attachment #9155768 - Attachment description: Bug 1644883: Shut down compositor thread on shutdown r=froydnj → Bug 1644883: Shut down Compositor thread on Shutdown r=mattwoodrow
Assignee: rjesup → nobody
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: