Open
Bug 1961571
Opened 23 days ago
Updated 22 days ago
Crash in [@ OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash_impl | js::AutoEnterOOMUnsafeRegion::crash | js::gc::AllocateTenuredCellInGC]
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: worcester12345, Unassigned)
Details
Crash report: https://crash-stats.mozilla.org/report/index/82567f06-452b-4dc2-b348-f688b0250421
MOZ_CRASH Reason:
[unhandlable oom] Failed to allocate new chunk during GC
Top 10 frames:
0 xul.dll MOZ_Crash(char const*, int, char const*) mfbt/Assertions.h:387
0 xul.dll js::AutoEnterOOMUnsafeRegion::crash_impl(char const*) js/src/vm/JSContext.cpp:1367
1 xul.dll js::AutoEnterOOMUnsafeRegion::crash(unsigned long long, char const*) js/public/Utility.h:313
1 xul.dll js::gc::AllocateTenuredCellInGC(JS::Zone*, js::gc::AllocKind) js/src/gc/Allocator.cpp:323
2 xul.dll js::gc::TenuringTracer::allocCell(JS::Zone*, js::gc::AllocKind, js::gc::Alloc... js/src/gc/Tenuring.cpp:750
2 xul.dll js::gc::TenuringTracer::alloc(JS::Zone*, js::gc::AllocKind, js::gc::Cell*) js/src/gc/Tenuring.cpp:711
2 xul.dll js::gc::TenuringTracer::allocString(JSString*, JS::Zone*, js::gc::AllocKind) js/src/gc/Tenuring.cpp:755
3 xul.dll js::gc::TenuringTracer::promoteString(JSString*) js/src/gc/Tenuring.cpp:1013
4 xul.dll js::gc::TenuringTracer::traverse(JS::Value*) js/src/gc/Tenuring.cpp:243
5 xul.dll js::gc::TenuringTracer::traceSlots(JS::Value*, JS::Value*) js/src/gc/Tenuring.cpp:676
Reporter | ||
Comment 1•23 days ago
|
||
138.0b3 (64-bit)
Comment 2•23 days ago
|
||
Please in your crash or bug reports post what you were doing at the time of the crash.
Flags: needinfo?(worcester12345)
Reporter | ||
Comment 3•23 days ago
|
||
Can't recall, but nothing fancy. Probably just opened the program.
Flags: needinfo?(worcester12345)
Comment 4•23 days ago
|
||
(In reply to Worcester12345 from comment #3)
Can't recall, but nothing fancy. Probably just opened the program.
If you write it immediately at the time of crash then you don't have to try to remember it later.
Comment 5•22 days ago
|
||
Since you've filed also other bugs about failed memory allocations, do check your hardware e.g. using MemTest86 or other similar hardware checkers.
You need to log in
before you can comment on or make changes to this bug.
Description
•