Closed
Bug 767973
Opened 13 years ago
Closed 13 years ago
IonMonkey: Assertion failure: entry->prop == shape, at jsinterp.cpp:964
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 772303
People
(Reporter: decoder, Unassigned)
References
Details
(Keywords: assertion, testcase, Whiteboard: [jsbugmon:update][ion:p1:fx18])
Attachments
(1 file)
|
7.81 KB,
application/zip
|
Details |
The attached testcase asserts on ionmonkey revision 2f9a29078126 (run with --ion -n -m).
| Reporter | ||
Comment 1•13 years ago
|
||
Note that this bug also reproduces with --no-ion. It also shows Valgrind errors when running in an opt build, like these:
==13246== Conditional jump or move depends on uninitialised value(s)
==13246== at 0x80B7ABA: PickChunk(JSCompartment*) (jsgc.cpp:628)
==13246== by 0x80C19F6: js::gc::ArenaLists::refillFreeList(JSContext*, js::gc::AllocKind) (jsgc.cpp:1480)
==13246== by 0x815CAF3: JSScript::Create(JSContext*, bool, JSPrincipals*, JSPrincipals*, bool, bool, js::GlobalObject*, JSVersion, unsigned int) (jsgcinlines.h:419)
==13246== by 0x81FBDC1: js::frontend::CompileScript(JSContext*, JSObject*, js::StackFrame*, JSPrincipals*, JSPrincipals*, bool, bool, bool, unsigned short const*, unsigned int, char const*, unsigned int, JSVersion, JSString*, unsigned int) (BytecodeCompiler.cpp:112)
Not sure if this is a problem on ionmonkey only, but it did not reproduce for me on m-c.
Comment 2•13 years ago
|
||
Can't reproduce with d85ca085f35d (tip).
| Reporter | ||
Comment 3•13 years ago
|
||
The test was quite unstable. Were you able to repro on the specified revision?
Updated•13 years ago
|
Whiteboard: [jsbugmon:update] → [jsbugmon:update][ion:p1:fx18]
Comment 4•13 years ago
|
||
I was able to reproduce this on the revision in comment 0.
It's a debug-only property cache bug, the following nativeContains call in PropertyCache::fullTest triggered a GC:
JS_ASSERT(pobj->nativeContains(cx, NameToId(name)));
The GC then zeroes the property cache table and we return an invalid PropertyCacheEntry. Bug 772303 fixed this by changing the nativeContains call to nativeContainsNoAllocation so that it will no longer trigger a GC.
Opening up since it's debug-only.
Group: core-security
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•