NoScript 2.1.1.2 CPU usage on Mac OS 10.6 and SeaMonkey 2.2

[Guest]

My computer is an i7-620M / 8 GB RAM MBP running Mac OS X 10.6.8.

I noticed NoScript is using about 10% CPU in SeaMonkey 2.2 even when there are NO browser windows open. I disabled NoScript and the CPU usage drops to below 1%.

Does it normally take up THAT much CPU?

[dhouwn]

Just to clarify this when you talk about NoScript CPU usage you mean the CPU usage of Firefox with NoScript activated.

Is it just the CPU or also the memory usage?

[Giorgio Maone]

NoScript does nothing until you load a web page, and even then it actually does something only during the load.
Does your problem happen on a clean profile with just NoScript installed?

[Guest]

This is the OP here.

To correctly test it, I have restarted the machine. Then I removed my SeaMonkey profile folder and launched SM. It created a new default profile. I then went into the preference and change the behavior on start up to "Display a blank page". I then quit SM and relaunched it.

The SeaMonkey process idled at ~1 - 2% CPU (via Activity Monitor)

I then installed the NoScript plugin and restarted the browser. With an empty browser window, the SM process idled at ~10 - 12% CPU.

I then disabled the NoScript plugin and restarted the browser. With an empty browser windows, the SM process idled at ~1 - 2% CPU.

Then I enabled the NoScript plugin again and restarted the browser. The SM process idled at ~10 - 12% CPU with an empty browser window.

[therube]

(Cannot confirm in Windows.)

As a test, does the same occur with FF 5.0.1 ?

[Guest]

This is OP here again.

Just tested with Firefox 5.0.1. The idle CPU usage is ~1 - 2% with either NoScript enabled or disabled.

[Giorgio Maone]

Just tested with Firefox 5.0.1. The idle CPU usage is ~1 - 2% with either NoScript enabled or disabled.

So, since NoScript has no special path either for SM 2.x or Mac OS X, and yours + therube's results, it would seem a Seamonkey bug triggered either by content policies or by script blocking on Mac OS X only.
Not exactly easy to diagnose, I'm afraid