Open Bug 1600494 Opened 2 months ago Updated Last month

Crash in [@ mozilla::recordreplay::parent::ChildProcessInfo::MaybePing]

Categories

(Core :: Web Replay, defect, P3)

defect

Tracking

()

People

(Reporter: jseward, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-e394c166-5839-4248-9868-7a1600191129.

This bug appears in 5 different installations of the OSX nightly 20191128094109.

Top 10 frames of crashing thread:

0 XUL mozilla::recordreplay::parent::ChildProcessInfo::MaybePing toolkit/recordreplay/ipc/ChildProcess.cpp
1 XUL mozilla::recordreplay::js::Middleman_WaitUntilPaused toolkit/recordreplay/ipc/JSControl.cpp:352
2  @0x3b5f5e52a1f3 
3  @0x1274563c7 
4  @0x3b5f5e4e3304 
5 XUL js::jit::MaybeEnterJit js/src/jit/Jit.cpp:200
6 XUL Interpret js/src/vm/Interpreter.cpp:3164
7 XUL js::RunScript js/src/vm/Interpreter.cpp:423
8 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:589
9 XUL js::ForwardingProxyHandler::call const js/src/proxy/Wrapper.cpp:162

Flags: needinfo?(bhackett1024)
Component: JavaScript Engine → Web Replay

I think what's happened here is that the child process has crashed (which we can recover from), but then the middleman process crashes (which we can't recover from) when it pings the child to make sure it hasn't hanged. This code has largely been rewritten in bug 1597149, and I don't think this problem will still occur after that bug lands.

Depends on: 1597149
Flags: needinfo?(bhackett1024)

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

For more information, please visit auto_nag documentation.

Flags: needinfo?(bhackett1024)
Flags: needinfo?(bhackett1024)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.