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)

Unspecified
Linux
defect
Not set
critical

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 ?
Component: Untriaged → XUL
Component: XUL → DOM: Content Processes
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).
Summary: Crash in libxul.so (deleted)@0xc4d2bb → Crash in libxul.so (deleted)@0xc4d2bb -- Crash Reason: MOZ_RELEASE_ASSERT(parentBuildID == childBuildID)
Hey Robert, is it something you could have a look at ?
Flags: needinfo?(robert.strong.bugs)
Current guess is that it happens when an update is ready AND at least 2 instances of the same binary are running.
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
Given I'm on Linux, will this be fixed in bug 1112937 as well ?
(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.
So maybe we can reopen this one ? :)
You need to log in before you can comment on or make changes to this bug.