InformAction Forums

My thought is that this is caused by Mozilla itself.
Contributing are Mozilla features such as Session Restore.
Further exacerbated by lack of physical memory, leading to paging of the Mozilla process.

This never occurred with SeaMonkey 1, but is common for me in SeaMonkey 2.

I have not removed NoScript to see if it may be otherwise.

Portmanteau wrote:I recently had a problem with Firefox continuing to run in the background after closing it.

This is often caused by an extension conflict or problematic toolbar. You may need to create a new profile, add NoScript, and then add any other extensions you have back one at a time until you find out which one is causing the problem. You can try the suggestions in these links first. They may point to the problem.

Firefox hangs
Problematic extensions - MozillaZine Knowledge Base
http://support.mozilla.com/en-US/kb/Bas ... ew_profile

Your experience with NoScript gone fixing your problem is mere coincidence and not even supported by anecdotal evidence, because I have multiple profiles and some of them don't even have NoScript on them and it hangs consistently and every time. I have noticed it occurs more with anything like a theme or XUL based extensions that use the core function that tend to hold on to it in memory because they are trying to operate on a timed function. So if you have anything like Brief, GreaseMonkey, AIO, RequestPolicy, BetterPrivacy, FEBE, Console2, Finjan, FireTray and Stylish to name a few. So I would say check with a clean profile, meaning NOTHING in it and then install NoScript and you will see, it will be very unlikely to get stuck, although Fx takes for ever to unload for the love of god which is just asinine but an issue for another discussion.