Closed Bug 941957 Opened 12 years ago Closed 9 years ago

crash in JS_CallHeapObjectTracer(JSTracer*, JS::Heap<JSObject*>*, char const*)

Categories

(Core :: JavaScript Engine: JIT, defect)

26 Branch
x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1198805

People

(Reporter: jbecerra, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-59909e6f-988a-4eb3-9ab0-be5332131120. ============================================================= The first few reports came in with fx26b1 but the number of reports increased starting starting beta 4. It's in the top 50 at the moment. There are no comments so there's little to go by. It seems to happen in Windows and the majority are in WinXP.
Crash Signature: [@ JS_CallHeapObjectTracer(JSTracer*, JS::Heap<JSObject*>*, char const*)] → [@ JS_CallHeapObjectTracer(JSTracer*, JS::Heap<JSObject*>*, char const*)] [@ JS_CallHeapObjectTracer]
Jon tells me JS_CallHeapObjectTracer has been renamed to TraceEdge, for which we still have crashes.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.