275176 - Stays in memory after it is closed. 100% cpu

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[David Park]

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

Stays in memory after it is closeed. 100% cpu. Does not unload from memory.

Reproducible: Always

Steps to Reproduce:
1.close mozilla
2.
3.

Actual Results:  
100% cpu and stays in memory

Expected Results:  
unload from memory and not go to 100% cpu

Comment 1

[Frank Wein [:mcsmurf]]

Is this a new problem (since you're using a nightly build)?

Comment 2

[Gérard Talbot]

I'm using Mozilla 1.8a6 build 2004121706 under XP Pro SP2 and I don't have such
problem.

Comment 3

[David Park]

Yes it is. I will get a new build today and see if it is still there.

Comment 4

[WADA:World Anti-bad-Duping Agency]

Bug 246909 also reported "not terminate" problem although it doesn't have
symptom of "cpu 100%".
Because both are termination problem, something wrong on server connection 
shutdown is suspected (especially mail&news).

Do you use mail&news?

If yes, can you get protocol log and attach log to this bug? (do not paste log data)
See http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop
Please do not forget to change "set NSPR_LOG_MODULES=protocol:5" to "set
NSPR_LOG_MODULES=POP3:5,IMAP:5,NNTP:5".
Please note that log file is overlayed on restart.

(1) Disable "Quick Launch" if you use
(2) Activate protocol log and start Mozilla mail&news
(3) Usual server access
(4) Close Mozilla(all of Browser, mail&news, ...)
    => Probably process is still active after window close
(4) Watch mozilla.exe process activity using "Task Manager"
    if you use MS Win-NT family(Win-2K,Win-XP)
(5) Wait for a while (more than 5 minutes).
(6) Kill mozilla.exe process and save protocol log file

Comment 5

[David Park]

It seems to be working fine now. Think tis was fixed in a new build. It good to
to keep an eye on it to make sure.

Comment 6

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #5)
Same question as my Bug 246909 Comment #16.
David Park, did you re-boot MS Win or logoff/re-login MS Win user after you
experienced this bug's problem?
If yes, did this bug's problem occur after the first re-boot or re-login
following the problem?

Comment 7

[David Park]

It does not seem to happen all the time.

Comment 8

[Gérard Talbot]

David, I don't understand why you do not answer WADA's specific questions, one
by one. We're all volunteers here doing QA work. Bugzilla is not a newsgroup
support; we're trying to confirm, identify and fix real bugs. The feedback we
expect from reporters should be within this frame of thinking; bugzilla
volunteers request and expect specifics, detailed useful info, verifiable info,
a set of steps to reproduce the problem you have. Vague, abstract, general
comment do not help.
http://www.mozilla.org/quality/bug-writing-guidelines.html
Keep in mind that there is over 8,000 bugreports with the status UNCONFIRMED
right now.

If you have a problem, best is to cooperate as thorough as possible and not
cause any useless waste of time. Furthermore if the problem is relatively
serious; it's in your best interests. Maybe this bug should be resolved as a
duplicate of bug 246909. I've been using the latest build all week long and I
have the same os you have; as far as I'm concerned, this bug should be resolved
as WORKSFORME.

Is your windows XP fully updated and patched?
Do you use Quick launch?
Do you use Mail & news application when this happens? If so, do you empty trash
folder on exit?
Do you have a lot of activated plugins when exiting mozilla.exe?... like Java
applet in a page in a tab, Acrobat Reader in a tab.

Comment 9

[Webmaster33]

I also noticed this big, especially, when JAVA plugin was launched by an applet
in the browser...

Comment 10

[Frederic Da Vitoria]

I don't know if it is related, but I had exactly the same problem with 1.8a6
build 2005010716... until I realized I was using an old version of MultiZilla
and I re-loaded it and installed the new version. The bug appeared when opening
and closing Mozilla browser, before accessing to any site. If I reloaded a new
instance of Mozilla before "cleaning" the old one, I got two instances in
memory, and if I closed the second instance, it stayed hidden in memory and used
cpu too and so on.

Comment 11

[Gérard Talbot]

No answer to repeated questions, no specifics, no reasonable way to reproduce
the problem, no reasonable way to identify a *_Mozilla_* problem with the info
provided. 
David, I have been using build 2004121706 for 3 days and never experienced the
problem you had.

Resolving as WORKSFORME