InformAction Forums

I had a really bad problem with Firefox eating up my CPU and growing in size, so I installed NoScript a while ago. It worked great for a while, then as I allowed more and more sites that were needed for pages that I was visited to work properly, my CPU problem returned (the memory usage problem is still there but to a lesser extent although I did just have it get to 1.5gb before having to cancel it because it was not responding). This tells me that I have obviously permitted one or more sites that cause problems with Firefox, but i have no idea which they are as I don't have any (obviously) malicious pages open. I do run FF with 40+ tabs open at one time so starting them one at a time to see when it starts looping is not a good option. Short of resetting the NoScript permission table to the original and starting over again with allowing new entries, is there anything I can do? Last time I checked in the FF forums, there was no way to find out which tab was causing the problems (I believe that is how I learned about NoScript).

The memory usage is surely excessive and hints at some extension leaking.
What's your extensions list?
Could you try running for a while with all your extensions (except NoScript) disabled and check if your problems persist?

I have to admit that I have seen strange behavior such as this with NoScript running but believe that any correlation is purely coincidental as it seems to be a failure and problem with Fx and some addons usage of particular substructure that may result in the leak and unreasonable performance. I have been dealing with it for a while now and managed to get my configuration (combination of addons, plugins, tweaks, etc) to a point where its a much lesser problem but its still there. Fx hanging after being closed, while running suddenly not being recognized by applications as a shell processor for URL protocol until you close it allowing the application to open a new instance, usually when that happens, it is a task manager process tree kill situation to fix. Now I am not saying that NoScript is absolutely not causing this, that I will leave up to Giorgio who is competent and most qualified to make that assertion but limited to my own opinion, its is unlikely to be an NS problem.