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

Status: NEW

(Core :: Web Replay, defect, P3)

Description

[Julian Seward [:jseward]]

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

Comment 1

[Brian Hackett [Laid off!]]

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.

Comment 2

[Release mgmt bot [:sylvestre / :calixte / :marco for bugbug]]

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

For more information, please visit auto_nag documentation.