Closed
Bug 627600
Opened 14 years ago
Closed 13 years ago
global shape changes don't blacklist
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: luke, Unassigned)
Details
This loop records N times since each iteration has a different global times:
for (var i = 0; i < 1000; ++i) {
this[i] = 3;
for (var j = 0; j < 15; ++j) {}
}
The problem is that things like "recordAttempts" etc are attached to the TreeFragment which is looked up via the tuple (global,globalShape,argc,pc), so each new global shape gets a new TreeFragment and fresh recordAttempts.
Since the vmfragments table is in the compartment, perhaps we can keep a map:
global -> shapeChangesAfterRecordingComplete
and when that gets too high for any global, we blacklist the whole global.
![]() |
Reporter | |
Comment 1•14 years ago
|
||
Alternatively, we could take globalShape out of the fragment key, put it into the TreeFragment, and then check it after looking up, doing blacklisting etc the normal way.
![]() |
Reporter | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•