108737 - initial window open [browser & mail] after install takes a long time

Status: VERIFIED INVALID

(SeaMonkey :: UI Design, defect)

Description

[sairuh (rarely reading bugmail)]

i seen this using 2001.11.06.12-commercial verif bits on linux [rh6.2]. not sure
how long this has been an issue, since i haven't been able to use daily trunk
builds consistently in the past week.

anyhow, to summarize, i've noticed that the *first* time after i install a
build, opening a browser or mail window for a given profile takes an awfully
long time. this is *no longer* a problem in subsequent window opening attempts
[new browser window, or reopening the mail window] during the same session *or*
even in subsequent sessions.

recipe:

0. install the 2001.11.06.12-comm linux build [in a unique dir].
1. i usually cancel out of the profile manager that pops up after installation
completes, but i think it's optional...
2. issue './netscape -P [profile-name]'

results: waited 27.48sec for the browser window to appear.

3. from this browser window, select Tasks > Mail & Newsgroups.

results: waited 25.28sec for the mail window to appear.

notes: i have multiple profiles, and this occurred for *each* profile i tested.
[neither of the profiles were new, however.]

not sure if this is a problem on win32 or mac, or even just 'a bad build'
issue...pls reassign as needed!

Comment 1

[Simon Fraser [no longer active]]

I wonder if this is fastload saving out the frozen XUL for the first time.

Comment 2

[sairuh (rarely reading bugmail)]

okay, jrgm and i did a couple more tests, and it seems that nfs [recent
networking foo in our bldg, woohoo] might be the culprit.

we compared a profile whose contents reside on a network drive [eg,
/u/sairuh/.mozilla/remote-profile] vs a profile residing locally [eg,
/tmp/local-profile/].

* case A: testing local-profile with its own XUL.mfasl. initially, it took about
4-5sec to start the browser; then 2-3sec for subsequent startups.

* case B: testing local-profile with a XUL.mfasl copied from the remote-profile.
initially, it was a bit slower than A, about 6sec [again, subsequent startup
faster]. but it's certainly not as bad as i had originally reported, where i was
launching remote-profile.

not sure what the networking [specifically nfs] situation is going to be in the
near future... i hope it's temporary, since i think many people might be running
profiles remotely...

Comment 3

[sairuh (rarely reading bugmail)]

s/hope it's/hope what i'm seeing is

Comment 4

[Brendan Eich [:brendan]]

Oh sure, blame FastLoad :-)

I always blame NFS, having implemented it in SGI's kernel in late 1985.

/be

Comment 5

[Cathleen]

base on sairuh's comment, NFS is the culprit.

Closing as INVALID.  Reopen, if this is not the case.

Comment 6

[sairuh (rarely reading bugmail)]

vrfy. i've switched over to using a local account primarily. :)