79521 - classic.jar is opened and read during startup

Status: RESOLVED WONTFIX

(SeaMonkey :: General, defect, P2)

Description

[Cathleen]

data from instrumenting startup code showing that we're opening and accessing 
files from classic.jar, even when modern skin is the default.

Need to figure out why and where this is happening, and fix that.

see data posted on http://mozilla.org/performance/startup-data/timings.html

Comment 1

[Blake Ross]

cc'ing dveditz, ssu.

Comment 2

[Daniel Veditz [:dveditz]]

What if you bypass the profile manager?

Comment 3

[Cathleen]

how do I bypass profile manager?  we only have one profile on the machine.

I am going to delete the old profile create a clean one today, and hook up with 
rogc and do another run of test to see if classic.jar is still being opened or 
not.

Comment 4

[timeless]

try -P profilename, however if you only have one profile i would hope it 
doesn't get loaded at all...

Comment 5

[Viswanath Ramachandran]

startup perf ==> pchen

Comment 6

[Cathleen]

new timeline data, with a clean profile, still showing classic.jar gets read 
during startup.

first launch:
http://mozilla.org/performance/startup-data/nscp-timings-reboot.html
relaunch:
http://mozilla.org/performance/startup-data/nscp-timings-warm.html

Comment 7

[Paul Chen]

yeah, we shouldn't be doing this, but it's not going to significantly reduce
startup time. pushing out to 0.9.2

Comment 8

[Viswanath Ramachandran]

Moving to mozilla1.0 timeframe, we're going to focus more on ironing out the
-turbo issues in m0.9.2. 

Comment 9

[Viswanath Ramachandran]

perf -> moving up a bit. 

Comment 10

[Paul Chen]

We open classic.jar as a result of calling nsChromeRegistry::InstallSkin(). I 
think that's valid, and that's the only reason we open classic.jar as far as I 
can tell. The timeline is a little misleading since you don't have more context 
to see why classic.jar is getting opened.

Marking wontfix, cc-ing hyatt to see if he wants to weigh in.