Closed Bug 1217649 Opened 10 years ago Closed 9 years ago

Intermittent loop/ui/index.html | Waiting for Completion - Could not find the test complete indicator (from gecko.log: Assertion failure: (ptrBits & 0x7) == 0 at js/Value.h:854)

Categories

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

Product:
Core
Component:
JavaScript: GC
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: crash, intermittent-failure, regression)

Crash Data

From the gecko.log attached to the failure, this is a crash: Assertion failure: (ptrBits & 0x7) == 0, at ../../dist/include/js/Value.h:854 #01: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x44876e8] #02: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x4487b66] #03: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x4519379] #04: JS_BasicObjectToString(JSContext*, JS::Handle<JSObject*>)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x3e1a79e] #05: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x4498c9e] #06: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x44973da] #07: js::RemoveRawValueRoot(JSContext*, JS::Value*)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x40dbb5a] #08: js::RemoveRawValueRoot(JSContext*, JS::Value*)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x40dbc31] #09: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x447e840] #10: JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x447e458] #11: js::GetElementsWithAdder(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSObject*>, unsigned int, unsigned int, js::ElementAdder*)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x3c43ae3] #12: js::GetElementsWithAdder(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSObject*>, unsigned int, unsigned int, js::ElementAdder*)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x3c4062d] #13: js::GetElementsWithAdder(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSObject*>, unsigned int, unsigned int, js::ElementAdder*)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x3c383eb] #14: js::GetElementsWithAdder(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSObject*>, unsigned int, unsigned int, js::ElementAdder*)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x3c39b7e] #15: JS_BasicObjectToString(JSContext*, JS::Handle<JSObject*>)[/builds/slave/test/build/application/NightlyDebug.app/Contents/MacOS/XUL +0x3d380fa]
Keywords: crash
Summary: Intermittent loop/ui/index.html | Waiting for Completion - Could not find the test complete indicator → Intermittent loop/ui/index.html | Waiting for Completion - Could not find the test complete indicator (from gecko.log: Assertion failure: (ptrBits & 0x7) == 0 at js/Value.h:854)
From the stack, guessing this is somewhere in core JS
Component: Client → JavaScript: GC
Product: Hello (Loop) → Core
Crash Signature: [@ JS::UnmarkGrayGCThingRecursively(JS::GCCellPtr)]
Keywords: regression
Note: the log gives a slightly different crash stack, but still starting at the same point: https://treeherder.mozilla.org/logviewer.html#?job_id=16113542&repo=mozilla-inbound
This (or something like it) spiked on the merge from aurora43 to beta43.
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Loop has been removed, no obvious signatures from last 6 months, hence closing.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.