Closed
Bug 71376
Opened 24 years ago
Closed 23 years ago
late-loading xpinstall ?
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P4)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.3
People
(Reporter: cathleennscp, Assigned: dveditz)
References
Details
(Keywords: perf, Whiteboard: [nav+perf])
So the rumor is that xpinstall is one of the components among others gets loaded
at start-up. :-) Due to the fact we are trying to improve start-up speed, is
it possible to delay the loading of xpinstall, with some lazy initialization,
till later?
Assignee | ||
Comment 1•24 years ago
|
||
There are two things in the way of this. One is changing the startup routine
(post-install replace) which is a bug almost checked in.
But the other reason is that we need to register and support the InstallTrigger
object, and the only way to do that is to register a name set at startup. Vidur
at one point said there was a plan to drive these from categories or something,
so that the component only needs to get instantiated when used. But I can't
find a bug that sounds like that so I'm not hopeful.
I'll nominate for the hell of it -- sure would be nice since 99% of the time
people don't need xpinstall functionality.
Assignee: dbragg → dveditz
Keywords: nsbeta1
adding perf keyword.
vidur, do you have any info on supporting init a component only at the time it's
requested?
Keywords: perf
Comment 4•24 years ago
|
||
I have bug 71982 partly fixed on my DOM/XPConnect branch, once that lands this
will be fixed, I might ask for some help with the xpinstall changes required on
the branch if that's ok?
Assignee | ||
Comment 5•24 years ago
|
||
Sure, I'll be happy to help (or have you help me) with the XPInstall change
once the DOM change is in.
Comment 6•24 years ago
|
||
The XPCDom landed, is this really fixed now?
Re-nominating since clearing away DLL loads is one of our best bets for real
startup perf improvements.
Assignee | ||
Comment 7•24 years ago
|
||
This is also dependent on the post-install replace bug, but should be doable
soon.
Comment 8•24 years ago
|
||
It's time to move this off m.9.1 milestone.
Assignee | ||
Comment 9•24 years ago
|
||
Ack, I've got the fixes, just waiting for Don's PIRU bug to land (he's seeking
a third round of reviews now)
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Comment 11•23 years ago
|
||
actually, reassigning back since dan has fixes. This will have to go in for RTM
or next release.
Assignee: syd → dveditz
Comment 13•23 years ago
|
||
moving to 0.9.3 because Dan is on sabbatical.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Assignee | ||
Comment 14•23 years ago
|
||
This has been fixed for a while. Big thanks to
dbragg -- for "post-install replaces"
jst -- XPCDOM made this possible, and he even changed our code
to start using the new mechanism for us
cathleen/waterson -- cleaning up after the "autoreg every time" hack I
put in right before my sabbatical because I ran out of time to
fix this one the right way.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 15•23 years ago
|
||
Marking Verified. Those have been in for quite awhile now.
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•