Closed
Bug 272489
Opened 20 years ago
Closed 17 years ago
Mozilla will not exit cleanly - high cpu and process does not close on shutdown
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jamesrome, Unassigned)
Details
Attachments
(1 obsolete file)
Build 2004113004 and 1.8a5. When I close Mozilla (file,Exit or clicking the X),
it does not close cleanly. I am left with part of a window showing, and the
mozilla process is still running. I must use task manager to close it. Lately
this happens all the time.
Reporter | ||
Comment 1•20 years ago
|
||
It also hangs mozilla if I exit the mail-news window while composing a message.
And wwhen Mozilla loads I get a message about a missing entry point
(In reply to comment #1)
> And wwhen Mozilla loads I get a message about a missing entry point
Please provide the full error message here. It seems your profile/installation
is corrupted.
Comment 3•20 years ago
|
||
Do you use "Run Filter on Folder"?
If yes, see Bug 266905.
Reporter | ||
Comment 4•20 years ago
|
||
I never heard of run filter, so I guess no.
Reporter | ||
Comment 5•20 years ago
|
||
I get this on startup
Comment 6•20 years ago
|
||
Note sure whether this really is the same bug but when I close Mozilla, it
seems to exit but the computer slows down enormously (much more than when it was
running).
If I check the running processes using Task Manager I see Mozilla taking 95+% of
the CPU. I can kill it from Task Manager but it will do the same, the next time
I open it.
As a test I started Internet Explorer (with Mozilla not running) and found that
after I open a new web page, the Mozilla icon appears on the IE page even though
it was not launched.
Comment 7•18 years ago
|
||
never seen this and doesn't look like anyone confirmed it either.
WFM current trunk
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 8•18 years ago
|
||
I still often get the SeaMonkey windows to close, but there is still a SeaMonkey process running, using up memory and cpu. It might be related to the acrobat plugin?? This is similar to comment #6
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 9•18 years ago
|
||
you mean simlar as in high cpu?
do you ever see it not close if you have NOT composed/sent a message?
ditto acrobat?
you no longer see attachment 167562 [details], right?
see also bug 360189
Summary: Mozilla will not exit cleanly → Mozilla will not exit cleanly - high cpu and process does not close on shutdown
Reporter | ||
Comment 10•18 years ago
|
||
correct. No error messages. I do see symptoms like 360189, but I have not pinned down what causes it. SeaMon key is mum about what it is doing. I think it is using lots of cpu, but not sure. I have 8 of them on my Mac, so not very noticeable.
Comment 11•18 years ago
|
||
does it happen with a clean, new profile (only mail accounts defined with no filters, no extensions, etc)?
Does it always close proper if you have NOT composed/sent a message? (and fail only you have composed a message?)
why do you suspect acrobat? does it only happen if you open a pdf?
xref: bug 283823
And Thunderburd has had a similar, but rare, issue.
Comment 12•18 years ago
|
||
(In reply to comment #8)
> I still often get the SeaMonkey windows to close, but there is still a
> SeaMonkey process running, using up memory and cpu.
> It might be related to the acrobat plugin?
Do you mean that process of seamonkey.exe will never disappear and high CPU utilization by seamonkey continues forever until you kill process seamonkey.exe from task manager?
If seamonkey.exe will never disappear until you kill process of seamonkey.exe from Task Manager, and if interfere by Adobe Reader plugin is suspected, read meta bug Bug 336184 and see bugs listed in dependency tree for Bug 336184 (including already closed bugs).
I don't know other problems than Bug 368821/Bug 383826 after release of Adobe Reader 8.
Comment 13•17 years ago
|
||
James, have you concluded that pdf (comment 12) is the cause of your problems?
Comment 14•17 years ago
|
||
Comment on attachment 167562 [details]
PNG file of error message
Obsolete, per comment 10.
Attachment #167562 -
Attachment is obsolete: true
Comment 15•17 years ago
|
||
(9+ months later)
No (more) reply from reporter(s).
SeaMonkey v1.0.x is not supported anymore.
(Would have been "Incomplete", now is) R.Invalid
Reopen if you can reproduce with SeaMonkey v1.1.9.
Status: REOPENED → RESOLVED
Closed: 18 years ago → 17 years ago
Resolution: --- → INVALID
Version: unspecified → 1.8 Branch
Reporter | ||
Comment 16•17 years ago
|
||
well, the latest SeaMonkey exhibits similar issues on shutdown. I am running it now inside a Fusion Virtiual Machine on my Mac. If I shut it down manually, it usually shuts down. But if I do a restart or shutdown, seamonkey never seems to respond to the shutdown message. I always get a message saying that seamonkey is not responding.
You need to log in
before you can comment on or make changes to this bug.
Description
•