Closed
Bug 1367101
Opened 7 years ago
Closed 7 years ago
Crash in libxul.so (deleted)@0xc4d2bb -- Crash Reason: MOZ_RELEASE_ASSERT(parentBuildID == childBuildID)
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1366808
People
(Reporter: julienw, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-fcd4b477-8c63-4180-8ffc-b84410170523. ============================================================= I'm not so sure about where to file this. I got several crashes that look like this: https://crash-stats.mozilla.com/report/index/fcd4b477-8c63-4180-8ffc-b84410170523 https://crash-stats.mozilla.com/report/index/4a4fbbc8-e83b-4e34-aa16-e89ee0170523 With the reason: MOZ_RELEASE_ASSERT(parentBuildID == childBuildID) I think this happens when an update is downloaded and applied and the browser is ready to restart to use the new update. Is it possible that a child is started with the ready update ?
Updated•7 years ago
|
Component: Untriaged → XUL
Reporter | ||
Comment 1•7 years ago
|
||
https://crash-stats.mozilla.com/report/index/2202f0b7-3103-47ee-ada9-ab4e30170531
Reporter | ||
Updated•7 years ago
|
Component: XUL → DOM: Content Processes
Reporter | ||
Comment 2•7 years ago
|
||
https://crash-stats.mozilla.com/report/index/6db3d20c-310d-4ca4-8b5d-c9f9b0170531
Reporter | ||
Comment 3•7 years ago
|
||
72 crashes in 1 week with this signature, is it relevant ? https://crash-stats.mozilla.com/search/?moz_crash_reason=%3DMOZ_RELEASE_ASSERT%28parentBuildID%20%3D%3D%20childBuildID%29&product=Firefox&date=%3E%3D2017-05-24T14%3A18%3A00.000Z&date=%3C2017-05-31T14%3A18%3A00.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports
Reporter | ||
Comment 4•7 years ago
|
||
Another bit of information is I usually have 2 concurrent instances running in the same time, on 2 different profiles. I don't think I got the issue before I used Nightly for my normal browsing (I always used it for my work).
Reporter | ||
Comment 5•7 years ago
|
||
https://crash-stats.mozilla.com/report/index/6db3d20c-310d-4ca4-8b5d-c9f9b0170531
Reporter | ||
Updated•7 years ago
|
Summary: Crash in libxul.so (deleted)@0xc4d2bb → Crash in libxul.so (deleted)@0xc4d2bb -- Crash Reason: MOZ_RELEASE_ASSERT(parentBuildID == childBuildID)
Reporter | ||
Comment 6•7 years ago
|
||
https://crash-stats.mozilla.com/report/index/1e6e4251-ffda-4df8-b9d8-2721b0170602
Reporter | ||
Comment 7•7 years ago
|
||
Hey Robert, is it something you could have a look at ?
Flags: needinfo?(robert.strong.bugs)
Reporter | ||
Comment 8•7 years ago
|
||
Current guess is that it happens when an update is ready AND at least 2 instances of the same binary are running.
Comment 9•7 years ago
|
||
This is a known issue that Robert is already working on in bug 1112937 for Windows. I'll dupe it to the generic bug. I don't know why the signature is weird.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(robert.strong.bugs)
Resolution: --- → DUPLICATE
Reporter | ||
Comment 10•7 years ago
|
||
Given I'm on Linux, will this be fixed in bug 1112937 as well ?
Comment 11•7 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #10) > Given I'm on Linux, will this be fixed in bug 1112937 as well ? No, I think that is Windows only. Separate bugs will presumably be needed for Linux and OSX.
Reporter | ||
Comment 12•7 years ago
|
||
So maybe we can reopen this one ? :)
You need to log in
before you can comment on or make changes to this bug.
Description
•