Closed Bug 561247 Opened 14 years ago Closed 12 years ago

"Assertion failure: pobj == found" with gczeal and eval on JM branch

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
status1.9.2 --- unaffected
status1.9.1 --- unaffected

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: assertion, testcase) 

This only happens on the JM branch, but does not require -m or -j.

gczeal(1);
for (let d in []) { }
for (let a = 0; a < 3; ++a) { eval(""); }

Assertion failure: pobj == found, at ../jsinterp.cpp:1940
Bug 561327 triggers the same assertion on TM branch.
js> gczeal(1);
js> for (let d in []) { }
js> for (let a = 0; a < 3; ++a) { eval(""); }

Doesn't assert with -a, -m, -n or the various combinations of that.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: in-testsuite?
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.