User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20100705 SeaMonkey/2.0.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20100705 SeaMonkey/2.0.5 While all the application windows do shut down, 236mb of ram and 6 to 15 percent of cpu time is used by Seamonkey still. It even continues to check for email and newsgroups. This continues for as long as user does not either shut down the system or kill the process. Reproducible: Always Steps to Reproduce: 1.Start Seamonkey 2.Open Mail/News 3.keep one of the two windows open for 5 minutes. Actual Results: When I shut the browser down and am not actively online for 48 hours, I do NOT expect thee application to contiinue checking email and consuming resources for that period. Expected Results: Seamonkey ran in the background for a weekend, downloading mail when it should have been shut down. With a fully up to date PCLinuxOS 2010 and their provided Seamonkey, it's a hit or miss on reproducibility. By getting the latest stable sources and building a debug build it actually aggravated it to an every time browser starts. I edited the sample mozconfig for a debug Firefox build to build the Suite. [ change one line was simplest way to go. ;) ] I am also running it from the build dir, rather than install / overwrite the distro supplied install.
- How did you shut down the browser? ("File => Quit" or Ctrl+Q ought to close everything, though sometimes several minutes after the last window closes, depending on number of [previously] open windows and tabs; clicking the [X] at top right of the browser ought not to close the mailer: this is intentional). - I would expect more than a one-line change between Firefox and SeaMonkey: please attach your mozconfig. - Do you also get this with SeaMonkey 2.1a2? (Don't use it on your usual profile: use a new profile, or a _copy_ of your usual.)
Created attachment 456491 [details] mozconfig Here's the mozconfig. and nope, this has only been tested with the stable release version. Apparently it is a known issue [ google groups support at least ] that is difficult to reproduce on Windows systems.
Severity: normal → critical
Version: unspecified → SeaMonkey 2.0 Branch
Attachment #456491 - Attachment mime type: application/octet-stream → text/plain
Please try with the following lines removed: ac_add_options --disable-libxul ac_add_options --disable-static ac_add_options --disable-ipc The last line has no effect on the 2.0 stable branch.
Just finished recompiling with those options removed, still happens. I think it might be an unintended side effect of the mail/news client staying active until session ended. If there are no open windows to any component of the suite, it needs to terminate everything and isn't. an addition to the ui to test for other open windows during closing down and if none terminate everything would likely fix it. it's odd to me that using the menu quit from any component terminates everything, not just that component. [ separate issue entirely ;) ] but it suggests the needed code for the above mentioned test for open windows and shut down everything is mostly in the code base already.
still there, in latest version of the 2 series. when closing the LAST open window of the suite, it does NOT matter if it's the menu file/quit or the 'x' the suite should clean up after itself. receive mail, then use the 'x' to close all open windows. seamonkey 2 does not shut down completely.
I doubt this is helpful but I've seen quite a few instances like this in many gecko/1.9.x based applications not just Seamonkey. Perhaps this is a non-issue in gecko/2 because I haven't noticed this crop up since I abandoned all gecko/1.9.x applications in day to day use.
I linux you can start SeaMonkey with gdb attached using the commandline (I think seamonkey -debug) to see what SeaMonkey is doing after closing the last open window.
do you have an ldap address book defined? if so, your issue may be resolved using *current* nightly source code. can you test it? otherwise, see https://wiki.mozilla.org/Thunderbird:Testing:Shutdown_Hang
Is this still reproducible with latest builds?
Severity: critical → major
Whiteboard: [Halloween2011Bug][CLOSEME 2012-01-01 WFM]
no idea I no longer use seamonkey for email because of this issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.