Closed Bug 1334211 Opened 8 years ago Closed 8 years ago

Crash in moz_abort | arena_run_split | arena_run_alloc | moz_xmalloc | mozilla::BufferList<T>::AllocateSegment

Categories

(Core :: IPC, defect)

Unspecified
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox51 --- affected
firefox54 --- affected

People

(Reporter: jujjyl, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-ff0e4d75-6f90-4028-9598-126962170126. ============================================================= An OOM crash in a location where we should not use infallible allocator, since these are potentially large allocations(?)
Why do you think that's an OOM? I think an OOM would be more like crashing through here: https://hg.mozilla.org/mozilla-central/annotate/fbdfcecf0c77/memory/mozalloc/mozalloc.cpp#l85 But instead we're crashing inside jemalloc itself, which is bad.
Crash volume for signature 'moz_abort | arena_run_split | arena_run_alloc | moz_xmalloc | mozilla::BufferList<T>::AllocateSegment': - nightly (version 54): 22 crashes from 2017-01-23. - aurora (version 53): 0 crashes from 2017-01-23. - beta (version 52): 0 crashes from 2017-01-23. - release (version 51): 570 crashes from 2017-01-16. - esr (version 45): 0 crashes from 2016-08-10. Crash volume on the last weeks (Week N is from 02-06 to 02-12): W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7 - nightly 15 6 - aurora 0 0 - beta 0 0 - release 362 108 0 - esr 0 0 0 0 0 0 0 Affected platform: Windows Crash rank on the last 7 days: Browser Content Plugin - nightly #110 #183 - aurora - beta - release #156 #215 - esr
Based on stats we haven't seen this since 53.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.