A Williams <[email protected]> wrote: > Seamonkey (2.20, Linux x64) is running most of the time on this machine. > No problems with that. Just occasionally I terminate the beast more > than a just few seconds before closing down. > > This is often a bad move. Seamonkey lives on, taking 100% of a cpu. I > have to 'kill' the process. > > I can't trigger (or not trigger) this reliably. It seems to make no > difference if I close the browser, the email client or the download > manager first - or last. This is not new with 2.20, this behaviour goes > back to before the legendary 2.18. > > Anyone else recognise this?
What I do see sometimes is that SeaMonkey has allocated a real lot of memory, much if which has been swapped out, and when I try to terminate it that takes a long time due to all the memory being swapped in again before being freed. This really loads the system, but not so much the CPU. Of course, when trying to start SeaMonkey before all of this has finished, nothing happens or a warning appears. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
