[FIXED] Allowing/blocking sites causes high CPU load

[D A]

Whatever changed in the 1.9.9.98rc releases have caused some kind of error when allowing or blocking sites. Whenever that action is taken the CPU. load goes up about 20-30% till it reaches 100% (of a 200% total on OS X). Downgrading to 1.9.9.97 resolves the issue. The error console isn't showing any errors. The CPU will remain active until Firefox is restarted.

My system:
MacBook Pro, C2D 2.4 GHz, 4GB RAM
Mac OS X 10.6.4
Latest Trunk release (error shows up since at least the 24th of June)
Default NoScript settings

Happens on a clean profile with no other extensions too.

Need any other information such as a sample of the Firefox process?

[Giorgio Maone]

I cannot reproduce.
However, does it keep happening if you set the noscript.autoReload.allTabs about:config preference to false?
If it does, does it when you uncheck NoScript Options|General|Automatically reload affected pages...?

[wbrckr]

hi,

I can confirm this. it started after the update this morning

- Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
- NoScript 1.9.9.98

the change in about:config and options:general did nothing to change the high load/temp.

[Giorgio Maone]

Thank you both for reporting.
This bug was actually not visible on Windows and Linux, where apparently most if not all the beta testers "live".
I finally managed to reproduce it on Mac OS X and fix it, please upgrade to 1.9.9.99 (or 1.9.9.99rc1 if you want to join the beta channel, where Mac users are very needed).

[wbrckr]

Thank you both for reporting.
This bug was actually not visible on Windows and Linux, where apparently most if not all the beta testers "live".
I finally managed to reproduce it on Mac OS X and fix it, please upgrade to 1.9.9.99 (or 1.9.9.99rc1 if you want to join the beta channel, where Mac users are very needed).

Hi Giorgio,
thanks for the qquick response + fix! Happy to join the beta-channel,
Tom

[D A]

I've upgraded to the beta channel and the fix appears to be working. No more high CPU load after allowing/blocking sites.

[becNS]

When trying to install the update, Firefox issues this error report:

Firefox could not install the file at

http://releases.mozilla.org/pub/mozilla ... +sm+fn.xpi

because: Invalid file hash (possible download corruption)
-261

[Giorgio Maone]

When trying to install the update, Firefox issues this error report:

Firefox could not install the file at

http://releases.mozilla.org/pub/mozilla ... +sm+fn.xpi

because: Invalid file hash (possible download corruption)
-261

This happens sometimes immediately after a release because Mozilla's mirrors are not in sync yet.
You can upgrade manually from the direct link here

[ncarvin]

Still getting 100 percent CPU usage with NoScript 1.9.9.99, Firefox 3.6.6, Mac OSX 10.6.4.

The only other Firefox add-on installed in AdBlock Plus 1.2.1.

When the problem occurs, sometimes after several hours of Firefox use, the Firefox will take 100 percent of one of two installed CPUs. The load will shift from one CPU to the other every few seconds.

The only way to end the problem is to quit Firefox.

I haven't yet noted a specific action that triggers the problem.

[GµårÐïåñ]

Still getting 100 percent CPU usage with NoScript 1.9.9.99, Firefox 3.6.6, Mac OSX 10.6.4.

The only other Firefox add-on installed in AdBlock Plus 1.2.1.

When the problem occurs, sometimes after several hours of Firefox use, the Firefox will take 100 percent of one of two installed CPUs. The load will shift from one CPU to the other every few seconds.

The only way to end the problem is to quit Firefox.

I haven't yet noted a specific action that triggers the problem.

I can confirm this, its not 100% of the time for me but it has happened 8 out of the 10 times I have started my browser today and with a profile without anything and/or with a profile that has NS disabled, it works fine. Its not a combination either, as far as I can tell, because it happens by itself as well as with others. Now, I will concede that the problem may not be directly NS but aggravated by it somehow, because I have seen this problem in the past with FX itself as well, but now its almost fully correlative.