Closed Bug 1520093 Opened 5 years ago Closed 5 years ago

Different output (NestTest mismatch) with testcase involving sameZoneAs

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: gkw, Assigned: jandem)

References

Details

(Keywords: testcase)

Attachments

(1 file)

function f(x) {
    print("1st: ",
        evalcx("(function() { return " + x + "; })()",
            newGlobal({
                sameZoneAs: null
            })));
    print("2nd: ",
        evalcx(x,
            newGlobal({
                sameZoneAs: null
            })));
}
f("this.y += 'ONCE';");

prints the following different (NestTest mismatch) output when they should possibly be the same, i.e. ONCE should only be printed once:

1st: undefinedONCE
2nd: undefinedONCEONCE

This may be a regression from m-c rev 450b8f0cbb4e and hence bug 1518753. Jan mentioned to file this over email. Tested on a 64-bit debug shell on m-c rev 8ec327de0ba7

===

$ ./js-dbg-64-linux-8ec327de0ba7 --fuzzing-safe testcase.js
1st: undefinedONCE
2nd: undefinedONCEONCE

$ ./js-dbg-64-linux-8ec327de0ba7 --fuzzing-safe --more-compartments testcase.js
1st: undefinedONCE
2nd: undefinedONCE

Flags: needinfo?(jdemooij)
Assignee: nobody → jdemooij
Status: NEW → ASSIGNED
Flags: needinfo?(jdemooij)
Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6ec84030fb70
Make evalcx work with same-compartment realms. r=jorendorff
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
No longer regressions: 1559974
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: