Closed
Bug 795896
Opened 12 years ago
Closed 11 years ago
UnwrapProxy is slow
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla21
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
In particular, it does xpc::WrapperFactory::IsXrayWrapper, which actually goes and does UnwrapObject (out of line, natch) and all sorts of crud like that. And some of the places we're calling it (e.g. getElementIfPresent, get) we already asserted !IsXrayWrapper. And some other places (finalize) we had better be able to assert it. Peter, are there other places we can assert it too? Presumably not getOwnPropertyDescriptor, right? What other hooks do Xrays call?
Assignee | ||
Updated•12 years ago
|
Blocks: ParisBindings
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Comment 2•12 years ago
|
||
Based on recent discussions with waldo, it sounds like I shouldn't be assuming that xrays will only call getOwnPropertyDescriptor... Which means I do need to keep doing conditional unwrap in all the hooks. :( I can at least make it not do random out of line calls, though.
Assignee | ||
Comment 3•12 years ago
|
||
Attachment #698761 -
Flags: review?(peterv)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bzbarsky
Whiteboard: [need review]
Updated•11 years ago
|
Attachment #698761 -
Flags: review?(peterv) → review+
Assignee | ||
Comment 4•11 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/19b9f064d8eb
Flags: in-testsuite-
Whiteboard: [need review]
Target Milestone: --- → mozilla21
Comment 5•11 years ago
|
||
Backed out because of build bustage: https://hg.mozilla.org/integration/mozilla-inbound/rev/d9e8e6757121 https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=32786d29daf8
Assignee | ||
Comment 6•11 years ago
|
||
Relanded; it had nothing to do with the bustage: https://hg.mozilla.org/integration/mozilla-inbound/rev/f68f04e1fa23
Comment 7•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f68f04e1fa23
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•