for (var a = 0; a < 4; ++a) { b = a; print(this.b) } causes different values to be output with and without -j on TM changeset cf557e3fc53d === $ ./js-opt-32-tm-darwin js> for (var a = 0; a < 4; ++a) { b = a; print(this.b) } 0 1 2 3 js> $ ./js-opt-32-tm-darwin -j js> for (var a = 0; a < 4; ++a) { b = a; print(this.b) } 0 1 2 2 js>

This seems very similar to bug 566637, yet has a different regressing changeset? Did that bug go away and come back, or is there a difference between the testcases that causes them to show different regressing changesets?

(In reply to comment #1) > This seems very similar to bug 566637, yet has a different regressing > changeset? Did that bug go away and come back, or is there a difference > between the testcases that causes them to show different regressing changesets? Hmmm, yeah it looks similar to bug 566637 - I'd leave it to someone more knowledgeable to confirm the dupe.

WFM on TM tip, assuming dupe to bug 566637..

Bug in removed tracer code, setting in-testsuite- flag.