186770 - WinXP launch is exceedingly slow (30 sec +) as it gets memory

Status: RESOLVED FIXED

(SeaMonkey :: General, defect)

Description

[william drescher]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

When launching in WinXP with the Windows Task Manager open to watch, mozilla
gets about 9 Meg of memory quickly and then sloooowly increases the assigned memory
(using the task manager "processes" tab to watch) to about 12 mb,where it opens
the display.  It still will not accept a url until memory grows (slowly)
further. Mozilla never takes more than 20% of cpu time, usually 3 - 7 %

When fully open with a page (this one), memory grows to 28,168 K and then all
runs fine. 
I have a pentium III, 450 Mhz with 312 Mb of Ram.  The profile is stored on a
SCO Unix server functioning as a file server, but the network is not limiting
the launch speed. (network is never more than 1% busy)

Reproducible: Always

Steps to Reproduce:
1. click on icon
2.watch
3. go out for coffee
4. watch some more
5 send out for pizza
6 eat the pizza
7 load url and browse

Comment 1

[william drescher]

During this load process no other program can launch either.
No swap is used.

Comment 2

[william drescher]

The problem appears to be in my profile.  I created a new profile and the
problem disapers.  It would be nice to know what is wrong in the profile so I
can salvage those items that are ok.

I will transfer files one by one from the old profile to the new and see if I
can isolate it.

Comment 3

[william drescher]

removing the XUL.mfl file from the profile directory fixed the problem.
Now it opens quickly, using 17 Mb of ram.

Comment 4

[william drescher]

WinXP Home
It seems that XUL.mfl is becoming corrupt (almost)every time I leave Mozilla. 
The symptom is that on the next restart it takes > 30 sec to start.  During this
time it is requesting and receiving up to 200 Mb of real memory and 500 Mb of
virtual memory.  Watching the memory assignments is fascinating, (using windows
task manager).
Phisical memory goes up and down,  as high as 200 mb and then as low as 3 Mb and
then up to 150 Mb and then down and then it settles at 17 Mb (for messenger) and
25 Mb for messenger and Navigator.


BTW,  the profile resides on a mapped drive on our server, not on the client
machine.

Comment 5

[Frederic Bezies]

Xul.mfl corrupted -> so a duplicate of bug 169777 ?

Comment 6

[Joe Infla]

William, is this problem still occurring?  The bug implicated in comment 5 was
fixed in April...

Comment 7

[william drescher]

Tthis bug can be marked as fixed.