Closed Bug 28911 Opened 20 years ago Closed 20 years ago
Need to avoid loading msgcompose and msgnews on startup
While command line processing, HandleArbitraryStartup() seems to be loading msgcompose and msgnews when starting up a browser. Each dll contributes to about .3 secs to startup time on an average on windows. I think the solution should be to add the commandArg, chromeUrl and pref in the registry. We should enumerate the registry and not have to create an instance of every commmand line handler to just get this info. The other sleazy thing to do would be to not run through all this if there was no command line (most of the time). The only thing to take care here is the pref for startup.
Nominating for beta1. Roughly startup took about 25 secs. Fixing this will give back about .6 secs not to mention the memory savings.
dp, you are right. alecf and I have talked about this, and we have an idea on how to fix it.
Status: NEW → ASSIGNED
Adding PDT- radar for beta1. Too risky at this time.
QA Contact: asadotzler → leger
What! you guys have no clue about the risk on this. The worst is -compose doesn't work. Please. Removing PDT- for reconsideration.
Putting on the PDT+ radar for beta1.
I'll get to this tomorrow, or later tonight.
Target Milestone: M14
lemme know if you need help
halfway done with fix now, will get alecf to review later tonight.
Whiteboard: [PDT+] → [PDT+] eta 2-25
full fix in hand, getting reviewed now. now, we only load the dlls if he have to. this should help startup time.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Yeah. I will pull and try.
Looks good with 000-02-29-09-M15 build. did not see these load on startup. Marking Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.