Closed
Bug 168907
Opened 23 years ago
Closed 20 years ago
Mozilla close perf on Linux / sometimes no close at all
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: 3.14, Unassigned)
References
Details
Attachments
(1 file)
|
20.98 KB,
image/png
|
Details |
I have observed that for a long time now (always trunk builds including the
latest). I use the Red Hat RPMs.
Sometimes, i.e., not reproducibly for me, Mozilla takes very long to close (from
closing the last window until ps x does not show any mozilla-bin process takes
longer than 30 seconds). Sometimes it never closes and I need to kill it manually.
Please let me know if I can do something to track down the reason.
pi
Comment 1•23 years ago
|
||
Reporter, what is your version ? (see Help | About Mozilla)
| Reporter | ||
Comment 2•23 years ago
|
||
As I said, the latest trunk RPMs, nothing new, not version dependend. Right now:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a) Gecko/2002091318
pi
Comment 3•23 years ago
|
||
could you check the memory consumption before you close? it's going to take a
long time to clean up if it's using a lot of memory.
| Reporter | ||
Comment 4•23 years ago
|
||
I will. But since I cannot intentionally reproduce this bug, it may take a while.
What I can tell you right now: If it happens and I use top it does not show
anything for mozilla-bin.
pi
| Reporter | ||
Comment 5•23 years ago
|
||
xosview showed a lot of memory consumption (about 121 Megs). Load and CPU were
at zero. Simply nothing happened.
It might be worth noting that I closed Mozilla since I ran into bug 142196.
pi
Comment 6•23 years ago
|
||
> xosview showed a lot of memory consumption (about 121 Megs)
ya, that sounds like a lot. If you don't have a lot of RAM (at least 256 MB),
it will take forever to exit. Using that much is certainly not normal, but it's
certainly possible (it does not necessarily indicate a bug).
| Reporter | ||
Comment 7•23 years ago
|
||
The machine has 128 Megs RAM. I do think, it is a bug, that the program does not
exit. It usually does, so there must be some special situations which causes the
failure.
pi
Comment 8•23 years ago
|
||
Mozilla will exit eventually, but if you're using that much RAM, it might not
happen in your lifetime.
in comment 5, are you saying that nothing happened when you tried to exit (and
no CPU usage, etc.)?
| Reporter | ||
Comment 9•23 years ago
|
||
Right. I closed all the windows (which happened immediately). Neither top nor
xosview showed any CPU activity, the load was at zero. I would expect that
Mozilla tries do do something, but that did not seem to be the case.
pi
| Reporter | ||
Comment 10•23 years ago
|
||
This time there was no real need to close Mozilla. Note, that the load was 0.0
and did only go up for ksnapshot.
pi
| Reporter | ||
Comment 11•23 years ago
|
||
I just had another incident of bug bug 142196. I closed Mozilla and it took 10
to 20 seconds to end all processes. So this is not a strong relationship.
pi
| Reporter | ||
Comment 12•23 years ago
|
||
*** Bug 171896 has been marked as a duplicate of this bug. ***
Comment 13•21 years ago
|
||
I'm not sure if this is the same bug or not, but I've noticed on my system that
if the last window I close is a mail-news window, it takes ages to close, but if
I close the mail-news window before I close browser windows it seems to close
faster. I've no idea why.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 14•20 years ago
|
||
in winxp i close seamonkey but then i check ctrl-alt-delete and its still in the process list, i have to kill it there for it to finally Really close. i dont hve quick launch enabled, and could not find another bug similar. i tried searching for "process close" "seamonkey won't close" but nothing. if someone could inform me where to post this bug, thank you. i expect seamonkey to close when there are no windows open.
Updated•20 years ago
|
Assignee: asa → general
QA Contact: asa → general
Comment 15•20 years ago
|
||
I think I've seen that mentioned somewhere, but perhaps not in bugzilla. What's needed are consistent steps to reproduce that problem (with a clean profile). If you have consistent steps, please file a new bug.
Boris: are you still seeing this bug?
| Reporter | ||
Comment 16•20 years ago
|
||
I am no longer using RedHat. With Debian (but I don't use it too often), I haven't seen it.
pi
Comment 17•20 years ago
|
||
Good enough for me
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 18•20 years ago
|
||
well i ditched seamonkey and am just using thunderbird and firefox separately now, that'll just have to be my workaround for this problem since it 'worksfor'you. both of those leave the process list as expected when they close. i have no idea why seamonkey wouldn't close completely though, it did it every time on me. i even waited a minute or two and still no. maybe its because i had multiple mail accounts. but hey, i've got my workaround, so i dont care =) it'll get fixed eventually. or not. whatever. have a nice day.
Comment 19•20 years ago
|
||
I resolved this bug because it worksforme and the original reporter. You aren't seeing this bug. In comment 15, I encouraged you to look elsewhere and/or file a new bug and I noticed you found bug 307154, which is more appropriate. But I'm still not seeing steps-to-reproduce starting with a clean profile. Without that, it's hard to fix any bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•