Closed Bug 1329305 Opened 5 years ago Closed 5 years ago

Crash in IPCError-browser | ShutDownKill (from GPUVideoImage::GetAsSourceSurface)

Categories

(Core :: Graphics: Layers, defect)

Unspecified
Windows 10
defect
Not set
critical

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)

This bug was filed from the Socorro interface and is 
report bp-a56bd372-c402-4032-8274-f61bf2170103.
=============================================================
Matt, related to bug 1300676?
Flags: needinfo?(matt.woodrow)
Attached patch check-dispatchSplinter Review
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
https://hg.mozilla.org/mozilla-central/rev/20672b7efd07
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
I assume the status for 52 is disabled since the GPU process is riding the 53 train?
Flags: needinfo?(matt.woodrow)
That is correct.
Flags: needinfo?(matt.woodrow)
You need to log in before you can comment on or make changes to this bug.