Closed Bug 315023 Opened 19 years ago Closed 7 years ago

nsXPConnect::InitClassesWithNewWrappedGlobal() creates temporary object for every pageload

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 720580

People

(Reporter: jst, Unassigned)

Details

It seems like there should be a way to do what nsXPConnect::InitClassesWithNewWrappedGlobal() does w/o the need to create a temporary object only to throw it away right away, for every page load. The temporarty object is used only to have a global with an xpc scope, we should look into either creating a new API that could take another object to use as the global while initializing the new wrapped global, or something along those lines. This could save us a bit on tP, though probably not all that much...
Assignee: dbradley → nobody
QA Contact: pschwartau → xpconnect
I don't think content windows use this method any more, so presumably it isn't an issue...
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
IIRC I fixed this in bug 720580 anyway.
Resolution: INCOMPLETE → DUPLICATE
You need to log in before you can comment on or make changes to this bug.