Closed Bug 1416560 Opened 7 years ago Closed 2 years ago

Crash in mozilla::ipc::SentinelReadError

Categories

(Core :: IPC, defect, P3)

Unspecified
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jseward, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-0f79bdcc-24d0-499e-8c8e-d9a5e0171110. ============================================================= This is topcrash #4 in the OSX nightly 20171109220104, Top 10 frames of crashing thread: 0 libmozglue.dylib MOZ_CrashPrintf mfbt/Assertions.cpp:50 1 XUL mozilla::ipc::SentinelReadError ipc/glue/ProtocolUtils.cpp:359 2 XUL mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:7810 3 XUL mozilla::ipc::MessageChannel::DispatchAsyncMessage ipc/glue/MessageChannel.cpp:2119 4 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2049 5 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1928 6 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1037 7 XUL NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:513 8 XUL mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:97 9 XUL MessageLoop::Run ipc/chromium/src/base/message_loop.cc:326 =============================================================
Flags: needinfo?(wmccloskey)
There aren't very many of these, and they don't seem to follow much of a pattern, at least for the MOZ_CRASH Reason field.
Flags: needinfo?(wmccloskey)
Priority: -- → P3

Large one day spike in the 3-6 build, but it appears to be a single installation.

Closing this as resolved:worksforme since there were no crashes in the last 6 months for this signature.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME

There have been crashes with this signature.

Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
QA Whiteboard: qa-not-actionable

Closing because no crashes reported for 12 weeks.

Status: REOPENED → RESOLVED
Closed: 3 years ago2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.