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?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to