Closed Bug 1562925 Opened 6 years ago Closed 5 days ago

Crash in [@ js::gc::GCRuntime::traceRuntimeCommon]

Categories

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

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox69 --- affected
firefox70 --- affected
firefox85 --- affected
firefox86 --- affected

People

(Reporter: julienw, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-d4fece8d-2867-4439-ab8a-ee1300190702.

Top 10 frames of crashing thread:

0 libxul.so js::gc::GCRuntime::traceRuntimeCommon js/src/gc/Cell.h:263
1 libxul.so js::gc::GCRuntime::traceRuntimeForMajorGC js/src/gc/RootMarking.cpp:285
2 libxul.so js::gc::GCRuntime::incrementalSlice js/src/gc/GC.cpp:7230
3 libxul.so js::gc::GCRuntime::gcCycle js/src/gc/GC.cpp:7686
4 libxul.so js::gc::GCRuntime::collect js/src/gc/GC.cpp:7866
5 libxul.so js::gc::GCRuntime::startGC js/src/gc/GC.cpp
6 libxul.so nsJSContext::GarbageCollectNow dom/base/nsJSEnvironment.cpp:1135
7 libxul.so InterSliceGCRunnerFired dom/base/nsJSEnvironment.cpp:1739
8 libxul.so mozilla::IdleTaskRunner::Run xpcom/threads/IdleTaskRunner.cpp:58
9 libxul.so mozilla::TimedOut xpcom/threads/IdleTaskRunner.cpp:78

This was on cnn. This happened after I profiled the loading of the page, then switched to another tab, but I don't know if that's related.

Blocks: GCCrashes

Adding 70 as affected. Trivial amount of crashes so far.

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)

No smoking gun. Low volume crash so setting P5 until rate increases or we get STR.

Flags: needinfo?(jcoppeard)
Priority: -- → P5

I believe I can modify the platform and product based on the crash reports with the same signature.
Furthermore, it seems that the crash might be a startup crash. NI me if steps to reproduce / causes of the issue are determined.

OS: Linux → All
Hardware: Unspecified → All
Severity: critical → S2

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: S2 → S3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 days ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.