Closed
Bug 1329305
Opened 9 years ago
Closed 9 years ago
Crash in IPCError-browser | ShutDownKill (from GPUVideoImage::GetAsSourceSurface)
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
FIXED
mozilla53
| Tracking | Status | |
|---|---|---|
| firefox51 | --- | unaffected |
| firefox52 | --- | disabled |
| firefox53 | --- | fixed |
People
(Reporter: milan, Assigned: mattwoodrow)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
|
1.31 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is
report bp-a56bd372-c402-4032-8274-f61bf2170103.
=============================================================
| Assignee | ||
Comment 2•9 years ago
|
||
Unfortunately we don't get a full stack, but my understanding is that this signature happens if the content process takes too long to shut down.
It's believable that our attempt to dispatch the task failed, and that's why we're stuck waiting forever.
Assignee: nobody → matt.woodrow
Flags: needinfo?(matt.woodrow)
Attachment #8825237 -
Flags: review?(dvander)
Attachment #8825237 -
Flags: review?(dvander) → review+
Pushed by mwoodrow@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/20672b7efd07
Don't wait on readback task if dispatching it failed. r=dvander
Comment 4•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox53:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
Comment 5•9 years ago
|
||
I assume the status for 52 is disabled since the GPU process is riding the 53 train?
Updated•9 years ago
|
Blocks: shutdownkill
Updated•9 years ago
|
Blocks: IPCError_ShutDownKill
You need to log in
before you can comment on or make changes to this bug.
Description
•