Open Bug 1582214 Opened 5 years ago Updated 6 months ago

Crash in [@ js::TenuringTracer::traverse<T>]

Categories

(Core :: JavaScript: GC, defect, P5)

Unspecified
Windows 10
defect

Tracking

()

Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- affected
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- fix-optional

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression, Whiteboard: qa-not-actionable)

Crash Data

We got a user on IRC today who has frequent content crashes on random sites

This bug is for crash report bp-a7792914-89f2-4f93-89bd-25dc70190917.

Other reports are
bp-4a175e89-e98d-4cf9-aa4f-8899f0190918
bp-d80c9e5b-c0f3-4c68-9196-b9fb70190917
bp-d2b1a408-f3bc-4396-a00b-f203d0190913

At least js::TenuringTracer::traverse<T> is new in 69 (it existed up to 64 but not for 65-67) and bug 1376646 touched code in that area. Yoshi, can you look if it's from that bug, please?

Top 10 frames of crashing thread:

0 xul.dll js::TenuringTracer::traverse<JSObject> js/src/gc/Marking.cpp:2759
1 xul.dll class mozilla::Maybe<JS::Value> js::MapGCThingTyped<`lambda at z:/task_1566864336/build/src/js/src/gc/Marking.cpp:2780:43'> js/public/Value.h:1311
2 xul.dll js::TenuringTracer::traceObject js/src/gc/Marking.cpp:2965
3 xul.dll js::Nursery::collectToFixedPoint js/src/gc/Marking.cpp:3249
4 xul.dll js::Nursery::doCollection js/src/gc/Nursery.cpp:963
5 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:839
6 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:8085
7 xul.dll nsresult mozilla::CycleCollectedJSContext::IsIdleGCTaskNeeded::IdleTimeGCTaskRunnable::Run xpcom/base/CycleCollectedJSContext.cpp:523
8 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1225
9 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486

Flags: needinfo?(allstars.chh)
Assignee: nobody → allstars.chh
Flags: needinfo?(allstars.chh)

Discussed during triage. Marking as fix optional for 69. Some of these signatures are high volume in beta.

(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #0)
It's interesting that the user is seeing all these different crash signatures. This suggests to me a problem with the user's machine rather than in the code.

The priority flag is not set for this bug.
:jonco, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jcoppeard)
Blocks: GCCrashes
Flags: needinfo?(jcoppeard)
Priority: -- → P5
Crash Signature: [@ js::TenuringTracer::traverse<T>] [@ js::ConstraintTypeSet::sweep ] [@ js::GCMarker::lazilyMarkChildren ] [@ js::ObjectGroup::sweep ] → [@ js::TenuringTracer::traverse<T>] [@ js::ConstraintTypeSet::sweep ] [@ js::GCMarker::lazilyMarkChildren ] [@ js::ObjectGroup::sweep ] [@ js::TenuringTracer::onObjectEdge]
Whiteboard: qa-not-actionable
See Also: → 1728842
Severity: critical → S2

This not really actionable at this time, so I making it an S3.

Severity: S2 → S3
Assignee: allstars.chh → nobody
You need to log in before you can comment on or make changes to this bug.