Closed Bug 1374278 Opened 7 years ago Closed 7 years ago

Crash in mozilla::layers::CompositorManagerChild::Init

Categories

(Core :: Graphics, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla56
Tracking Status
firefox-esr52 --- unaffected
firefox54 --- unaffected
firefox55 --- unaffected
firefox56 --- fixed

People

(Reporter: aosmond, Assigned: aosmond)

References

Details

(Keywords: topcrash, Whiteboard: gfx-noted)

Crash Data

Attachments

(1 file)

Assignee: nobody → aosmond
Blocks: 1365927
Status: NEW → ASSIGNED
Crash Signature: [@ mozilla::layers::CompositorManagerChild::Init ]
Priority: -- → P3
Whiteboard: gfx-noted
Crash Signature: [@ mozilla::layers::CompositorManagerChild::Init ] → [@ mozilla::layers::CompositorManagerChild::Init ] [@ mozilla::layers::CompositorBridgeParent::InitSameProcess ]
I should also note that the previous race between CompositorBridgeChild::ActorDestroy and GPUChild::ActorDestroy also existed prior to bug 1373540. However since it always created a new top-level protocol for each compositor, it wasn't a problem, since it didn't care about the previous state. With CompositorManagerChild, we *do* care, and that's where the problems arose from.
Adding topcrash keyword. After 20170621102301 and the fix for Bug 1373540 there are still a few hundred crashes, so that puts this signature at the top part of crash-stats.
Keywords: topcrash
Attachment #8880402 - Flags: review?(dvander) → review+
Pushed by aosmond@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b59e819dfaa5
Fix a race condition between GPUChild and CompositorManagerChild when the GPU process crashes. r=dvander
https://hg.mozilla.org/mozilla-central/rev/b59e819dfaa5
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: