Crash in [@ arena_t::PallocHuge | Allocator<T>::moz_arena_malloc]
Categories
(Core :: Memory Allocator, defect)
Tracking
()
People
(Reporter: sefeng211, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/a67a4088-86e6-42a5-984e-1476e0200502
Top 10 frames of crashing thread:
0 firefox-bin arena_t::PallocHuge memory/build/mozjemalloc.cpp:3713
1 firefox-bin Allocator<MozJemallocBase>::moz_arena_malloc memory/build/malloc_decls.h:51
2 firefox-bin replace_moz_arena_malloc memory/replace/phc/PHC.cpp:1435
3 libxul.so js::LifoAlloc::allocImplColdPath js/public/Utility.h:384
4 libxul.so js::jit::VirtualRegister* js::jit::TempAllocator::allocateArray<js::jit::VirtualRegister> js/src/jit/JitAllocPolicy.h:58
5 libxul.so js::jit::BacktrackingAllocator::go js/src/jit/BacktrackingAllocator.cpp:862
6 libxul.so js::jit::GenerateLIR js/src/jit/Ion.cpp:1421
7 libxul.so js::jit::CompileBackEnd js/src/jit/Ion.cpp:1483
8 libxul.so js::jit::IonCompileTask::runTask js/src/jit/IonCompileTask.cpp:27
9 libxul.so js::HelperThread::ThreadMain js/src/vm/HelperThreads.cpp:2050
This is a linux only crash, and all crashes happen at 0x0. It doesn't happen very frequent, however it looks like it's an legit crash.
Glandium, can you take a look?
|
||
Comment 1•5 years ago
|
||
The crash reason is: [unhandlable oom] Failed to mmap, likely no more mappings available /builds/worker/checkouts/gecko/memory/build/mozjemalloc.cpp
This looks like an OOM crash, and one that is mostly happening inside the JS engine.
|
Reporter | |
Comment 2•5 years ago
•
|
||
That makes sense. I think I was only staring at the crash address 0x0..
|
||
Updated•5 years ago
|
| Comment hidden (Intermittent Failures Robot) |
|
||
Comment 4•5 years ago
|
||
The severity field is not set for this bug.
:glandium, could you have a look please?
For more information, please visit auto_nag documentation.
|
|
||
Comment 5•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
|
||
Updated•5 years ago
|
Description
•