Closed
Bug 646255
Opened 15 years ago
Closed 15 years ago
TI changes behavior of { Object.preventExtensions(this); Proxy; }
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 642307
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: testcase)
$ js-dbg-64-f6a77f725bbc-darwin
js> try { Object.preventExtensions(this); Proxy; } catch(e) { print(e); }
TypeError: Proxy is not extensible
$ js-dbg-64-f6a77f725bbc-darwin -m -a -n
js> try { Object.preventExtensions(this); Proxy; } catch(e) { print(e); }
({})
The error message seems strange, so I don't know which behavior is correct and which mode has a bug.
This difference-between-modes goes back at least until the point at which TI moved from a compile-time flag to a command-line flag (autobisect fingered bug 637674).
| Reporter | ||
Updated•15 years ago
|
Blocks: infer-regress
Comment 1•15 years ago
|
||
This is bug 642307 --- there is a bug in TM that preventing extensions on the global object breaks lazy standard class initialization. Inference does the lazy resolution at an earlier point (during analysis, which can trigger crashes), producing the different behavior.
Later today I'll push a fix so that inference doesn't try to resolve standard classes ahead of time, which should cause things to be broken in the same way on the TM and JM branches.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•