Closed
Bug 898532
Opened 12 years ago
Closed 5 years ago
Crash Report [@ js::gc::ArenaLists::unmarkAll() ]
Categories
(Core :: JavaScript Engine, defect, P5)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: vic.garin, Unassigned)
References
Details
(Keywords: crash)
Crash Data
https://crash-stats.mozilla.com/report/index/bp-62dc9a18-316c-4a7e-8c5a-83c4e2130726
and
https://crash-stats.mozilla.com/report/index/bp-646ac48b-221e-483e-afc5-fc9812130726
not sure if I am supposed to post anything else here?
I don't have steps to reproduce.
Keywords: crash,
crashreportid
Comment 1•12 years ago
|
||
It's a kind of GC crash that won't be fixed without STR.
Assignee: nobody → general
Status: UNCONFIRMED → NEW
Component: General → JavaScript Engine
Ever confirmed: true
Keywords: crashreportid
Product: Firefox → Core
Hardware: x86_64 → All
Comment 2•12 years ago
|
||
far more common is
zzz_AsmCodeRange_Begin | js::gc::ArenaLists::unmarkAll()
which appears to be same stack
bp-d983f625-f489-4131-be36-d357a2131112
#89 crash for Fx 25.0 for zz_AsmCodeRange_Begin...
js::gc::ArenaLists::unmarkAll is not in top 300
Crash Signature: [@ js::gc::ArenaLists::unmarkAll() ] → [@ js::gc::ArenaLists::unmarkAll() ]
[@ zzz_AsmCodeRange_Begin | js::gc::ArenaLists::unmarkAll() ]
Comment 3•11 years ago
|
||
me bp-164e04da-c35e-4545-9a52-023652140325 My recollection is firefox was using a few hundred MB - nothing abnormal. windows flickered ("not resopnding" perhaps?).
oddly, perhaps mere coincidence, svchost.exe was at 600mb and growing.
bp-f14effee-ed9e-4425-b419-e6a742140324 is of a user who crashes frequently this past month. Half the crashes are this signature. Other sigs are
TraceJSHolder bp-7effeadc-24a1-4d14-8e14-b8a3e2140220
JSCompartment::sweepBaseShapeTable() bp-9314ffaf-1fcc-4cc9-beb8-3f7d72140225
JS::Zone::isCollecting() bp-49f83f4f-200a-42fd-a770-e9a4f2140213
Comment 4•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Assignee: general → nobody
Updated•10 years ago
|
Crash Signature: [@ js::gc::ArenaLists::unmarkAll() ]
[@ zzz_AsmCodeRange_Begin | js::gc::ArenaLists::unmarkAll() ] → [@ js::gc::ArenaLists::unmarkAll() ]
[@ zzz_AsmCodeRange_Begin | js::gc::ArenaLists::unmarkAll() ]
[@ js::gc::ArenaLists::unmarkAll ]
[@ zzz_AsmCodeRange_Begin | js::gc::ArenaLists::unmarkAll ]
Comment 5•7 years ago
|
||
I don't think this is going to be actionable. ONlhy a few dozen crashes per month for current veresions (The graph in the bug report is incorrect - there isn't ~150 crashes per day) and in the past two weeks [1] only about two dozen crashes for current versions.
[1] https://crash-stats.mozilla.com/signature/?signature=js%3A%3Agc%3A%3AArenaLists%3A%3AunmarkAll&date=%3E%3D2018-03-21T04%3A58%3A14.000Z&date=%3C2018-04-04T04%3A58%3A14.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=version&_sort=-date&page=1
Has STR: --- → no
Flags: needinfo?(sdetar)
Comment 6•7 years ago
|
||
This does not see to be actionable at this time. I making it a P5.
Flags: needinfo?(sdetar)
Priority: -- → P5
Comment 7•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•