I used a simple tool called "filemon" to monitor which files are opened by Mozilla during startup. If I interpret the log-file correctly, the Chrome.jar files are opened and closed several times subsequently, without actually reading any data (see item 15130 and following and 17942 and following of the attachment). Similar for the prefs (see item 932 and following). You can download the tool at http://www.sysinternals.com/ I have absolutely no idea what component this might be, so I put it to Browser-General.
Adding perf keyword and makring as blocker for bug 7251 (improve startup performance tracking bug).
over to toolkit for evaluation
Assignee: asa → trudelle
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm
Assignee: trudelle → hyatt
This is the JAR protocol.
Assignee: hyatt → neeti
Component: XP Toolkit/Widgets → Networking
QA Contact: jrgm → tever
this sounds like bug 72551, which Dan Veditz has checked in a fix for it around 4/5/01. Can reporter, Christian Matter email@example.com, verify if this is indeed the same bug as 72551?
Looking at the filemon-logs, it seems to be much better, although there's still improvement to be made IMO. I'll attach a new logfile with the important sections marked sometime later this afternoon.
I checked the log-file again and it actually looks pretty good right now. Marking as dup. *** This bug has been marked as a duplicate of 72551 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
-> XP Misc + qa
Status: RESOLVED → VERIFIED
Component: Networking → XP Miscellany
QA Contact: tever → brendan
You need to log in before you can comment on or make changes to this bug.