Nightly 58 x64 20171108110838 de_DE f63559d7e6a570e4e73ba367964099394248e18d @ Debian Testing (KDE, Radeon RX480) This happened while testing bug 1415272. bp-65ab3605-c8a2-4dfd-b650-a12610171108 08.11.17 18:27 bug 1415609 [@ mozilla::gfx::RecordedScaledFontCreationByIndex::PlayEvent ] bp-2cbc91a4-520d-4460-8d7f-31f730171108 08.11.17 18:27 [@ mozilla::ipc::MessageChannel::Send | mozilla::layers::PAPZCTreeManagerChild::SendUpdateZoomConstraints

bug 1350566 additionally also has this crash signature. (URLs of some crash signatures have a problem where there are two spaces (%20) after "|", which makes two signatures out of one and Socorro can't detect that. As text, those signatures are identical. This is why I didn't see the other one at first.) (Kartikaya Gupta (email:kats@mozilla.com) from bug 1350566 comment 4) > I'm fairly sure this isn't actually a threading problem, but the IPC channel is getting closed. That AssertWorkerThread function is just how it manifests. Is the quoted comment applicable to this crash, too? (bp-2cbc91a4-520d-4460-8d7f-31f730171108) If yes, this would be a duplicate of bug 1350566, I think. bug 1415609 crashed my gpu process (closed a channel?), so the content process couldn't send this message?

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #1) > > Is the quoted comment applicable to this crash, too? I believe so, yes. > (bp-2cbc91a4-520d-4460-8d7f-31f730171108) > If yes, this would be a duplicate of bug 1350566, I think. > bug 1415609 crashed my gpu process (closed a channel?), so the content > process couldn't send this message? Yeah that sounds correct. I don't think I realized in bug 1350566 that this would occur in the case of GPU process crashes but that makes sense, and is something we should guard against. I'll dupe this over and leave a comment there.