Open
Bug 1180980
Opened 9 years ago
Updated 2 years ago
Consider adding a parent count to SavedFrame objects for internal use
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: fitzgen, Unassigned)
References
(Blocks 2 open bugs)
Details
This would allow js::SavedStacks::adoptAsyncStack to return early and avoid two O(n) traversals when the async stack is in the right compartment and the number of parents is less than our maximum.
Comment 1•9 years ago
|
||
(In reply to Nick Fitzgerald [:fitzgen][:nf] from comment #0) > This would allow js::SavedStacks::adoptAsyncStack to return early and avoid > two O(n) traversals when the async stack is in the right compartment and the > number of parents is less than our maximum. This is nice but wouldn't help much with the case we're optimizing for, that is the iterative async calls, where the parent count exceeds the maximum allowed frames and we need to get close to the root anyways to recreate the stack. So I'm not sure whether by itself it can justify the memory and complexity overhead.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•