Closed Bug 1407001 Opened 7 years ago Closed 7 years ago

Crash in mozilla::gfx::GPUProcessManager::SimulateDeviceReset

Categories

(Core :: Graphics, defect)

Unspecified
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla58
Tracking Status
firefox-esr52 --- unaffected
firefox56 --- wontfix
firefox57 --- wontfix
firefox58 --- fixed

People

(Reporter: rhunt, Assigned: rhunt)

Details

(Keywords: crash, Whiteboard: [gfx-noted])

Crash Data

Attachments

(1 file)

This bug was filed from the Socorro interface and is 
report bp-309c41e9-60f7-44b8-a12a-bde340171009.
=============================================================

It looks like 'screen_composited_changed_cb' can run before gfxPlatform::Init() is called. I think this can only happen when we are showing the profile manager.

I don't think it makes sense to call gfxPlatform::Get() to force initialization here, because we don't have any compositors that need to be reset. We should be able to just skip this callback when this happens.
Attachment #8916705 - Flags: review?(lsalzman)
Attachment #8916705 - Flags: review?(lsalzman) → review+
Pushed by rhunt@eqrion.net:
https://hg.mozilla.org/integration/mozilla-inbound/rev/50073b51fc10
Don't reset compositors for composited changed callback when GPUProcessManager is null. r=lsalzman
https://hg.mozilla.org/mozilla-central/rev/50073b51fc10
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
This looks low-frequency enough that we can let it ride the trains.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: