Closed
Bug 1278085
Opened 9 years ago
Closed 9 years ago
Crash in jemalloc_crash | je_free | js::PropertyTree::getChild
Categories
(Core :: WebRTC: Audio/Video, defect, P1)
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
People
(Reporter: marco, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-38536460-02c7-4c57-be38-f60ae2160604.
=============================================================
Crashed while starting a WebRTC call on https://apprtc.appspot.com/.
Looks like the crash happened while interpreting some JavaScript code, but I can see mozilla::MediaManager::NotifyRecordingStatusChange up in the stack.
https://hg.mozilla.org/integration/mozilla-inbound/annotate/f3740cfc4b04/memory/mozjemalloc/jemalloc.c#l4731 - Probably `arena` was null here.
| Reporter | ||
Comment 1•9 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #0)
> https://hg.mozilla.org/integration/mozilla-inbound/annotate/f3740cfc4b04/
> memory/mozjemalloc/jemalloc.c#l4731 - Probably `arena` was null here.
Actually, I guess the assertion failed and so MOZ_CRASH explicitly writes to 0
in order to cause a crash.
Comment 2•9 years ago
|
||
Marco, are you able to repro? It's a bit hard to pinpoint exactly what the cause is. I'd say part of the heap has been trashed maybe ?
Component: Audio/Video → WebRTC: Audio/Video
Flags: needinfo?(mcastelluccio)
| Reporter | ||
Comment 3•9 years ago
|
||
No, unfortunately I can't. I'll comment again if I find a way to reproduce it.
Flags: needinfo?(mcastelluccio)
Comment 4•9 years ago
|
||
Paul, is this actionable? Unsure how to triage this one?
Flags: needinfo?(padenot)
Updated•9 years ago
|
Rank: 15
Priority: -- → P1
Comment 5•9 years ago
|
||
Maire, what would be the correct way to triage this real but non-actionnable bug?
Flags: needinfo?(padenot) → needinfo?(mreavy)
Comment 6•9 years ago
|
||
I agree this is not actionable. When we have a non-actionable bug that no one can repro AND we think it's unlikely that it will reproduced soon, we typically close the bug as INCOMPLETE. If anyone can repro this with more info in the future or anyone can think of a way to get more info out of a future crash, we should reopen.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(mreavy)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•