Closed Bug 752391 Opened 14 years ago Closed 7 years ago

crash in js::gc::MarkRange

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
15 Branch
Platform:
All
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox15 - ---

People

(Reporter: jaws, Unassigned)

Details

(Keywords: crash, regression, Whiteboard: [js:nonactionable])

Crash Data

This bug was filed from the Socorro interface and is report bp-2786f9bb-3491-48fe-aa30-7fe312120506 . =============================================================
It started spiking in 15.0a1/20120504122939. The regression range is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2db9df42823d&tochange=9ebf3dc839c5 It's probably related to incremental GC. More reports at: https://crash-stats.mozilla.com/report/list?signature=js%3A%3Agc%3A%3AMarkRange%3CJSObject%3E
Keywords: regression
OS: Windows NT → Windows 7
Hardware: x86 → All
Version: Trunk → 15 Branch
It's #7 top crasher in today's build.
tracking-firefox15: --- → ?
Keywords: topcrash
Crash Signature: [@ js::gc::MarkRange<JSObject>] → [@ js::gc::MarkRange<JSObject> ]
For now, the spike was temporary, and so this looks like another of the usual GC mark phase topcrashes. If it spikes again or we get some STR, then we can do something.
Whiteboard: [js:nonactionable]
Keywords: topcrash
Nonactionable, and currently low, so unmarking.
tracking-firefox15: + → -
Assignee: general → nobody
Crash Signature: [@ js::gc::MarkRange<JSObject> ] → [@ js::gc::MarkRange<JSObject> ] [@ js::gc::MarkRange<T> ]
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.