220781 - mozilla-bin keeps running after quit and eats all memory

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Paul Libbrecht]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/85 (KHTML, like Gecko) OmniWeb/v496
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv. 1.5) Gecko/20030925

Since quite long, Mozilla's quit function on Linux seem to leave a mozilla-bin process always 
running. That's not so bad though it should be justified somewhere...

But now this process eats all the memory (more than 80% on a freshly restarted 1Gb RAM)... and 
keeps the swapd so busy that it feels like a freeze.
It's also very hard to kill. It takes sometimes 4 to 5 times of kill -9 to get at the end of this monster.

Reproducible: Always

Steps to Reproduce:
1. Launch Mozilla
2. Quit Mozilla
3. Use top to see the process creeping...
 (or "ps -auxwww | grep -i mozilla")
Actual Results:  
mozilla-bin is first, eating all memory.

Expected Results:  
Shut-up.

I think there were an amount of Full-Circle reports sent... about a day ago... [e-mail] 
as address.

Comment 1

[Ivchikx]

I have the same problem (On WinXP SP2). Normally when I quit mozzilla app.,
there have to be one service running, that takes ~15000K... But several times
there are two services, one with 15000k and other with larger amount loaded in
memory... If I want to start browser again, I see window, that asking for
profile choose, becouse default profile is already in use (I think with that
other-unnormal service)...

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.