Closed Bug 1215195 Opened 9 years ago Closed 9 years ago

continued abort crash in mozilla::layers::PImageBridgeChild::Write

Categories

(Core :: Graphics: Layers, defect)

x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Tracking Status
firefox42 + wontfix
firefox43 + wontfix

People

(Reporter: kairo, Assigned: nical)

References

Details

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

Crash Data

[Tracking Requested - why for this release]: +++ This bug was initially created as a clone of Bug #1208071 +++ Even after the fix in bug 1208071, we still have crashes with this signature, even though a reduced amount, those are 1.5% of 42.0b6 crashes right now. Examples are bp-e8f793ed-457e-4e14-9496-1f1d32151014 or bp-9c634c8a-9e5c-4546-9f6d-214ef2151014 Nical, any idea what's up here?
Flags: needinfo?(nical.bugzilla)
Tracking as it is an important crash.
Whiteboard: [gfx-noted]
I have a STR, see Bug 1213344 Comment#9
Are all of the remaining crashes shutdown?
Assignee: nobody → nical.bugzilla
(In reply to Milan Sreckovic [:milan] from comment #3) > Are all of the remaining crashes shutdown? No idea, I don't know how I could check for that.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #4) > (In reply to Milan Sreckovic [:milan] from comment #3) > > Are all of the remaining crashes shutdown? > > No idea, I don't know how I could check for that. I was naively assuming that metadata ShutdownProgress set to xpcom-shutdown indicated that we were in shutdown procedure, perhaps that's not the case?
Shutdown hangs are sad but not big enough to track that late in the cycle. Untracking.
But tracking for 43.
Flags: needinfo?(nical.bugzilla)
Still a topcrash in 43 beta, but marking wontfix as we are a week from release. I don't see either of these signatures in 44 or 45, perhaps a good sign.
This is another symptom of bug 1207220: some video frames which hold on to gfx resources are still alive during/after gfx shutdown.
Depends on: 1207220
No crash since bug 1209039 landed (nightly and aurora). There's another bug that should have helped with this on beta as well but I don't have the bug number handy.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.