Page 1 of 1
Noscript versions newer 1.9.9.36 cripple FF3.0.17
Posted: Thu Feb 04, 2010 9:15 pm
by KevinRose
Noscript versions newer than 1.9.9.36 cause huge slowdowns and CPU spikes on firefox 3.0.17 on both XP and Linux. I've gone up to .45 and walked back one (available) rev at a time and .36 in the newest version that doesn't do this.
I have no idea why, but makes a site that takes 1-2 seconds with NS inactive (or globally allow set) take more like 30-60 seconds. A good test is Google image search.
Re: Noscript versions newer 1.9.9.36 cripple FF3.0.17
Posted: Thu Feb 04, 2010 9:35 pm
by Giorgio Maone
Google Image Search is working like a charm (page load time well under 1 second) with latest NoScript and Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.0.17) Gecko/2009122116 Firefox/3.0.17.
Could you check whether you're observing this slow-down even with NoScript as the only extension enabled?
If the problem goes away, you may want to try
Standard Diagnostic seeking for a conflict.
Re: Noscript versions newer 1.9.9.36 cripple FF3.0.17
Posted: Fri Feb 05, 2010 12:50 am
by KevinRose
I've tried that and it's still slow. I get ~9 seconds to search for "cute kittens" w NS.45 and under 1 second to complete with it disabled or running NS.36. Even the google home page takes a long time to load with NS enabled.
My corker with linux and FF3.0.17 has left for the day, but I find that even allowing all scripts globally didn't help on XP (He said it did for him on Linux), I have to actually disable NS and restart FF to get it to stop hammering on the CPU and being very slow with every web page.
Re: Noscript versions newer 1.9.9.36 cripple FF3.0.17
Posted: Fri Feb 05, 2010 5:57 am
by Alan Baxter
I'm not seeing any of these issues at all with Fx 3.0.17 on Windows XP SP3. I'm using a new test profile that has only NoScript installed, using NoScript's default settings.
There may be a problem caused by Kevins' NoScript settings or whitelist. He should click Reset in the NoScript Options dialog to see if that resolves his problem. If that's not sufficient, then it sounds like Kevin's profile may have gotten messed up somehow. He needs to start over with a new profile, don't change any settings, and test with only NoScript installed using only its default settings.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.17) Gecko/2009122116 Firefox/3.0.17
Default theme
NoScript 1.9.9.45 using default settings
Edit: Instructions for making a new profile and transferring settings from the old, problematic profile to the new one which works properly.
http://support.mozilla.com/en-US/kb/Bas ... ew_profile