Closed Bug 1617773 Opened 4 years ago Closed 2 months ago

Crash in [@ mozilla::ipc::MessageChannel::DispatchSyncMessage]

Categories

(Core :: IPC, defect, P3)

ARM
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox75 --- affected
firefox90 --- affected

People

(Reporter: ash153311, Unassigned)

References

Details

Crash Data

This bug is for crash report bp-4877ceab-9757-4032-b80f-be0180200225.

Top 10 frames of crashing thread:

0 xul.dll mozilla::ipc::MessageChannel::DispatchSyncMessage ipc/glue/MessageChannel.cpp:2196
1 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2133
2 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1220
3 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:481
4 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
5 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
6 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
7 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
8 xul.dll nsAppShell::Run widget/windows/nsAppShell.cpp:406
9 xul.dll nsAppStartup::Run toolkit/components/startup/nsAppStartup.cpp:271

This crash is probably Fission related: 39 of 43 crash reports for 75.0a1 have Fission enabled. We have crash reports with this signature before 75.0a1, but they have fewer than ten reports per Nightly cycle.

Fission Milestone: --- → ?
Component: General → DOM: Content Processes

low volume, wait and see

M6

Nika suspects this might be related to session history changes, but we don't know if the pref is enabled. Can we include "session history in parent" pref value in crash reports' telemetry environment?

Fission Milestone: ? → M6

The priority flag is not set for this bug.
:neha, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(nkochar)

P3. Crash volume is pretty low. Only 30 crash reports total for all of 73.0.x Release.

Flags: needinfo?(nkochar)
Priority: -- → P3

Moving to IPC component because the crash is not in DOM code. This is not a Fission bug.

Crash because message sender did not set a reply handler?

Fission Milestone: M6 → ---
Component: DOM: Content Processes → IPC

Bug 1600186 comment #4 was an attempt at making sense of a similar crash.

I have just encountered this crash on the Beta 90.0.0-beta.1 with Samsung Galaxy Tab A6 (Android 5.1.1).

e28e1bbe-a236-4fae-a354-8248a52c815d
<native crash>


<native crash>

I do not have STR. I had only 4 tabs opened, I was signed in, no add-ons installed.

Hardware: Unspecified → ARM
Severity: normal → S3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.