Closed Bug 1361111 Opened 7 years ago Closed 7 years ago

Crash in mozilla::ipc::MessageChannel::AssertWorkerThread | mozilla::ipc::MessageChannel::Send | mozilla::layers::PWebRenderBridgeChild::SendDeleteImage

Categories

(Core :: Graphics: WebRender, defect)

Other Branch
Unspecified
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox-esr52 --- unaffected
firefox53 --- unaffected
firefox54 --- unaffected
firefox55 --- fixed

People

(Reporter: kats, Assigned: kats)

References

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

This bug was filed from the Socorro interface and is 
report bp-fd000008-6f87-4437-b49e-82af60170501.
=============================================================

Got this pretty much on startup with webrender enabled on a clean profile. Looks like we're trying to do some IPC on a closed channel because the GPU process crashed previously and we're reinitializing.
Comment on attachment 8863467 [details]
Bug 1361111 - Avoid sending IPDL messages over a dead channel.

https://reviewboard.mozilla.org/r/135258/#review138272

How about another PWebRenderBridge messages?
I see a lot of PWebRenderBridge message sending without checking.
Attachment #8863467 - Flags: review?(hshih) → review+
In this case at least I only care about the GPU process reset case. There we explicitly call destroy on the WR LayerManager, and so code invoked from that destroy method should not assume the IPC channel is still working. It's true that the channel might get torn down during, say, a transaction, but I haven't seen that happen yet.
Pushed by kgupta@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9530e0ce7d55
Avoid sending IPDL messages over a dead channel. r=jerry
https://hg.mozilla.org/mozilla-central/rev/9530e0ce7d55
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: