Closed Bug 1616202 Opened 5 years ago Closed 5 years ago

Intermittent PID 14108 | ==16125==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x7f78023c72ff bp 0x7fff9d58aeb0 sp 0x7fff9d58ace0 T0)

Categories

(Core :: IPC, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1493656

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

That bug summary is not informative; it communicates that there was a MOZ_CRASH somewhere in an ASan build (segfault on address 1), on the main thread of some process (T0), and nothing else. The other parts of the message are essentially random numbers. In particular, the assertion failure could have been anywhere in the entire codebase.

The log, however, is more informative:

#0 0x7f78023c72fe in mozilla::ipc::MessageChannel::Clear() /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:786:9
#1 0x7f78023c5e16 in mozilla::ipc::MessageChannel::~MessageChannel() /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:650:3
#2 0x7f78023ff9c2 in mozilla::ipc::IToplevelProtocol::~IToplevelProtocol() /builds/worker/workspace/build/src/ipc/glue/ProtocolUtils.h:392:32
#3 0x7f7806efbeed in mozilla::gmp::GMPContentParent::~GMPContentParent() /builds/worker/workspace/build/src/dom/media/gmp/GMPContentParent.cpp:35:39

This is another MessageChannel destroyed without being closed assertion failure.

Group: core-security-release
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Group: core-security-release
You need to log in before you can comment on or make changes to this bug.