Closed Bug 1623981 Opened 5 years ago Closed 5 years ago

Replace JSWindowActor::ReceiveRawMessage MOZ_DIAGNOSTIC_ASSERT with a MozCrashPrintf that reports the name of the crashing message

Categories

(Core :: DOM: Content Processes, task, P2)

task

Tracking

()

RESOLVED DUPLICATE of bug 1605209

People

(Reporter: cpeterson, Unassigned)

References

(Blocks 1 open bug)

Details

This change will help diagnose IPC message crashes like bp-1ec19da7-8bfc-4eea-9b7e-c7a030190705 in bug 1563825.

Chris, is there any update on this? It's been P1 and unassigned for a while.

Flags: needinfo?(cpeterson)

(In reply to Julien Cristau [:jcristau] from comment #1)

Chris, is there any update on this? It's been P1 and unassigned for a while.

I'll reduce the priority to P2. This is a nice-to-have Fission debugging task we'd like implement soon. We don't need to track this bug as a release blocker.

Flags: needinfo?(cpeterson)
Priority: P1 → P2

Bug 1605209 added a AutoAnnotateMessageInCaseOfCrash with the name of the message to JSActor::ReceiveRawMessage.

For instance, if you look at this recent crash report bp-a3c71472-8e2f-4cc1-845a-1b0150200617 in the meta data tab, "JSActorMessage" is "RuntimeMessage" and "JSActorName" is "Conduits".

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE

Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.

Fission Milestone: M6a → ---
You need to log in before you can comment on or make changes to this bug.