Closed
Bug 700668
Opened 13 years ago
Closed 13 years ago
Don't enumerate all compartments for every traversal of a XPCWrappedNative
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
mozilla11
People
(Reporter: peterv, Assigned: peterv)
References
Details
Attachments
(1 file)
6.27 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
This is showing up in profiles in bug 696761. We should only look for expando objects if we know we ever had one for the XPCWrappedNative that we're traversing. Patch coming up.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #572839 -
Flags: review?(mrbkap)
Comment 2•13 years ago
|
||
So without this patch we do O(number of live compartments) work for every XPCWrappedNative that we traverse?
That could certainly explain the profiles I'm seeing, if I have lots of compartments and lots of XPCWrappedNatives around....
Updated•13 years ago
|
Attachment #572839 -
Flags: review?(mrbkap) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Target Milestone: --- → mozilla11
Comment 4•13 years ago
|
||
Is this something we could safely backport?
Comment 5•13 years ago
|
||
For what it's worth, I just checked and I seem to have 425 compartments in the compartment map over here... Is there any way we could just avoid the linear scan?
Comment 6•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•