Closed
Bug 641655
Opened 14 years ago
Closed 7 years ago
Standard class stuff shouldn't be lazy on global objects
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: Waldo, Assigned: Waldo)
References
()
Details
This is part of the reason why 15.2.3.4-4-1.js from the test262 stuff breaks.
Assignee | ||
Comment 1•14 years ago
|
||
Gaaah, I mislabeled http://hg.mozilla.org/tracemonkey/rev/069715a705c2 which really referred to bug 650369.
Comment 2•7 years ago
|
||
I see consistent numbers here. I imagine it's been fixed at some point so it should be a dupe. But RESOLVED WORKSFORME works too?
Flags: needinfo?(jwalden+bmo)
Comment 3•7 years ago
|
||
WebIDL window calls JS_NewEnumerateStandardClasses when you try to Object.getOwnPropertyNames on it, which resolves all the lazy stuff.
Assignee | ||
Comment 4•7 years ago
|
||
If this works, best killing off this bug, yeah. I still think the standard-class stuff needs to be not so lazy in some way that doesn't chew up too much memory, but a seven-year-old neglected bug clearly isn't the right place for something like that to happen.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jwalden+bmo)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•