Mike C <[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 > From a previous post: (6/14/2013) > > It may be that SeaMonkey didn't shut down properly on some > occasion. If that happens, a file called 'parent.lock' is created, > which prevents another instance of SeaMonkey from running. > > With SeaMonkey closed, locate the SeaMonkey 1.x profile, you should > find it here: > > C:\Documents & Settings\<Your Windows User Name>\Application > Data\Mozilla\Profiles\default\xxxxxxxx.slt > > Where 'xxxxxxxx' is a random eight-character string. > > The file 'parent.lock', if present, should be in the folder > 'xxxxxxxx.slt', if it is delete it.
You probably got this advise from an old article somewhere. It is outdated. It no longer works that way. There is no longer any need to perform this procedure. The parent.lock file is always created and a file lock is held on it. This means that you cannot remove the file when Seamonkey is running, and when it is (properly) closed it is possible to remove the file. However, this is not required as the termination of the program automatically releases the lock on the file, and that is what Seamonkey checks for when starting. So, the existence of a parent.lock file no longer is a problem. In the past, it was. Then when a parent.lock existed the program would not start (and the file was removed on clean exit). _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
