If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Crash in mozalloc_abort | Abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::dom::PContentChild::Read




DOM: Service Workers
6 months ago
6 months ago


(Reporter: marcia, Unassigned)


(Blocks: 1 bug, {crash})

53 Branch
Mac OS X

Firefox Tracking Flags

(firefox53 affected, firefox54 unaffected, firefox55 unaffected)


(crash signature)



6 months ago
This bug was filed from the Socorro interface and is 
report bp-02c5ca94-847a-4fc5-b3cc-2764a2170328.

This crash is new in 53 beta 5 and showed up on the explosiveness report: http://bit.ly/2mMvJsV

All the crashes seem to be confined to Mac OS and affects all versions of Mac OS.

Not sure which component this belongs in - I just made my best guess.

Comment 1

6 months ago
Does anyone know why this doesn't have a crash reason annotation?
Flags: needinfo?(erahm)

Comment 2

6 months ago
As phillip pointed out this has not been seen after Beta 5, so we can close it out if it doesn't reappear.
IPC was a reasonable start, but I looked at a half dozen of these and they all have stuff like mozilla::dom::PContentChild::Read(nsTArray<mozilla::dom::ServiceWorkerRegistrationData>*, IPC::Message const*, PickleIterator*) in the stack, so this is or was some service worker issue, I think.
status-firefox54: --- → unaffected
status-firefox55: --- → unaffected
Component: IPC → DOM: Service Workers
From the array, I'd guess this is the PContent InitServiceWorkers message.
(In reply to Benjamin Smedberg [:bsmedberg] from comment #1)
> Does anyone know why this doesn't have a crash reason annotation?

It looks like we only annotate in the parent process, but this was from the child process [1].

[1] https://hg.mozilla.org/releases/mozilla-beta/annotate/62467dd7218f/ipc/glue/ProtocolUtils.cpp#l302
Flags: needinfo?(erahm)

Comment 6

6 months ago
Ooh, we should fix that! That probably dates from the days where crash annotations in children were main-thread-only.


6 months ago
Blocks: 1328631
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.