On Mon, Jan 13, 2014 at 9:17 AM, A Williams <[email protected]> wrote: > Chuck wrote: >> >> I am having a problem with Seamonkey clearing out of memory after closing. >> I have a CPU monitor and can see it using 100% for over 2 minutes after >> closing. >> I cannot restart it without going to Task Manager and killing it during >> those 2+ minutes. >> Any suggestions? >> Thanks, >> Chuck > > > Leaving the entire theoretical discussion of semaphores and file-rights > aside, I have a similar problem on this Linux machine since the upgrade to > 2.23.
I have had this problem occasionally with Firefox, SeaMonkey, and even just the npviewer, since way back when I was using CentOS 5 (now on Xubuntu 12.04/3.8 kernel). I just wrote a simple shell script that clobbers whichever one is giving me trouble: #!/bin/bash # A shell script to kill that annoying runaway seamonkey/firefox/npviewer that won't die case `basename $0` in "seakill") cmd=seamonkey;; "foxkill") cmd=firefox;; "npvkill") cmd=npviewer;; *) echo "Unrecognized command."; exit 1;; esac /usr/bin/pkill -9 $cmd /bin/ps -fC $cmd Hope that helps. MR _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
