Crash in [@ OOM | small]
Categories
(Core :: JavaScript Engine, defect, P2)
Tracking
()
People
(Reporter: worcester12345, Unassigned)
References
(Blocks 1 open bug)
Details
Crash report: https://crash-stats.mozilla.org/report/index/81bf1add-4275-4e8f-83fe-541180211024
MOZ_CRASH Reason: MOZ_CRASH()
Top 10 frames of crashing thread:
0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1240
1 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1256
2 xul.dll js::TenuringTracer::onObjectEdge js/src/gc/Tenuring.cpp:79
3 xul.dll js::gc::TraceEdgeInternal<JS::Value> js/src/gc/Marking.cpp:768
4 xul.dll js::TypedRootedTraceableBase<js::StackRootedTraceableBase, JS::StackGCVector<JS::Value, js::TempAllocPolicy> >::trace js/public/RootingAPI.h:924
5 xul.dll js::gc::GCRuntime::traceRuntimeCommon js/src/gc/RootMarking.cpp:321
6 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:1099
7 xul.dll js::gc::GCRuntime::collectNursery js/src/gc/GC.cpp:4125
8 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:4091
9 xul.dll js::NewStringDontDeflate<js::CanGC, unsigned char> js/src/vm/StringType.cpp:1689
Reporter | ||
Comment 1•3 years ago
|
||
First crash in quite a while. This one looks different than the others.
Comment 2•3 years ago
|
||
Hi,
Can you provide steps to reproduce the crash?
Best,
Clara
Reporter | ||
Comment 3•3 years ago
|
||
Sorry, I cannot. This was after leaving it on overnight. I came back to Chrome running, and Firefox not running. They were both running before.
Comment 4•3 years ago
|
||
Alright, I'll try that on my end to try replicate the crash. Thanks!
Can you also attach your about:support information?
Best,
Clara
Comment 5•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Over the last week, we have 4700 crash reports with js::TenuringTracer::onObjectEdge
.
Jon / Steve, would you know how to investigate this issue?
Updated•3 years ago
|
Reporter | ||
Comment 7•3 years ago
|
||
(In reply to Clara Guerrero from comment #4)
Alright, I'll try that on my end to try replicate the crash. Thanks!
Can you also attach your about:support information?
Best,
Clara
I'd rather not put this information out in public. Can I email it to you instead?
Comment 8•3 years ago
|
||
It's actually for dev team to analyze the information and investigate the cause (either by an installed add-on or your specifications)
I haven't experienced this crash on my end though. How many tabs did you have open while leaving computer on with ff overnight?
Best,
Clara
Reporter | ||
Comment 9•3 years ago
|
||
(In reply to Clara Guerrero from comment #8)
It's actually for dev team to analyze the information and investigate the cause (either by an installed add-on or your specifications)
I haven't experienced this crash on my end though. How many tabs did you have open while leaving computer on with ff overnight?
Best,
Clara
Many. Over a hundred.
Updated•3 years ago
|
Comment 10•2 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Comment 11•2 years ago
|
||
Any reason to believe this crash (which is already gone from crash-stats) is any diferent from bug 1712262? Or the multitude duped to bug 1673778?
Comment 12•2 years ago
|
||
It's an out of memory crash. The specific stack in the description is for OOM while collecting the nursery (for which we have bug 1472062). The signature is totally generic though. Since it's gone from crash-stats, I'll just dupe this bug.
Updated•2 years ago
|
Description
•