Closed
Bug 1568057
Opened 5 years ago
Closed 5 years ago
Crash in [@ OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenuredSlow]
Categories
(Core :: JavaScript: GC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1472062
People
(Reporter: yoasif, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-38da6857-3edd-4272-af4a-efaf80190722.
Top 10 frames of crashing thread:
0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1477
1 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1490
2 xul.dll js::TenuringTracer::moveToTenuredSlow js/src/gc/Marking.cpp:2918
3 xul.dll class mozilla::Maybe<JS::Value> js::MapGCThingTyped<`lambda at z:/task_1563383129/build/src/js/src/gc/Marking.cpp:2652:43'> js/public/Value.h:1323
4 xul.dll js::gc::StoreBuffer::SlotsEdge::trace js/src/gc/Marking.cpp:2707
5 xul.dll js::gc::StoreBuffer::MonoTypeBuffer<js::gc::StoreBuffer::SlotsEdge>::trace js/src/gc/Marking.cpp:2671
6 xul.dll js::Nursery::doCollection js/src/gc/Nursery.cpp:941
7 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:786
8 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:7873
9 xul.dll js::gc::GCRuntime::gcIfRequested js/src/gc/GC.cpp:7930
Report from a post on reddit: https://www.reddit.com/r/firefox/comments/cgeb9i/whats_up_with_the_memory_usage/
User has 32GB RAM and is getting OOM crashes. The report shows that the physical memory used by his computer was 49.
Comment 1•5 years ago
|
||
This is a different signature for Bug 1472062
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Comment 2•5 years ago
|
||
(In reply to Asif Youssuff from comment #0)
User has 32GB RAM and is getting OOM crashes. The report shows that the physical memory used by his computer was 49.
The crash report says that the user has 5.64 MB page file free out of 90 GB so that may be related.
Comment 3•5 years ago
|
||
Yes, that's what we were discussing both on reddit and now on Bug 1472062. This one is a duplicate because it's the same crash.
You need to log in
before you can comment on or make changes to this bug.
Description
•