InformAction Forums

NoScript versions 2.6.8.7 and newer on Firefox 3.6 result in Firefox's memory usage quickly rising to two times normal levels after a bit of browsing and having 15-30 tabs open. Every so often, maybe every 0.5 to 2 minutes, Firefox will freeze for a short moment. Freezes seem to take longer and appear more often when Firefox uses more memory. Firefox's CPU usage jumps to 100% during freezes. Even though I can't quantify it, newer versions of NS seem to be getting worse with every release.

I first noticed the problem with NS 2.6.8.7 and I managed to hold out for a few days before downgrading. With NS 2.6.8.12, the freezes annoyed me too much after maybe 10 minutes.

Downgrading to NS 2.6.8.6 always brings the memory usage back to normal levels and the freezes are gone.

Does it help if you upgrade Fx to 3.6.28 (if you can)?
https://ftp.mozilla.org/pub/mozilla.org ... n32/en-GB/

Not possible at the moment, sorry.

I tried to reproduce with no success.
Maybe an extensions conflict? Could you try Standard Diagnostic?

Sorry for the delay. I finally found the time to somewhat reliably test this.

I performed the following tests like this:
1. Always had 15 tabs open (non-trivial content).
2. Opened a few additional tabs (non-trivial content).
3. Closed additional tabs.
4. Checked memory usage.
5. Goto 2.

I tested NS 2.6.8.6, 2.6.8.7 and 2.6.8.12. I made sure not to change any other settings besides changing NS versions and enabling/disabling additional extensions.

Scenario A: NS 2.6.8.7 and 2.6.8.12 with all other extensions enabled
- Freshly started Fx with 15 tabs takes up about 100 MiB.
- Opening and closing tabs increases memory usage; Fx becomes more and more jerky as memory usage increases.
- At about 300 MiB, Fx freezes for several seconds and memory usage goes down to about 200 MiB. Jerkiness is somewhat reduced. This happened after opening and closing roughly 50-100 tabs in total.
- Opening and closing tabs increases memory usage and jerkiness again.

Scenario B: NS 2.6.8.7 and 2.6.8.12 with all other extensions disabled
- Same as scenario A, but all memory usage figures about 10 MiB lower.

Scenario C: NS 2.6.8.6 with all other extensions enabled
- Freshly started Fx with 15 tabs takes up about 100 MiB.
- Opening tabs increases memory usage to somewhere above 150 MiB, depending on content.
- Shortly after closing the additional tabs, memory usage always goes down to about 150 MiB. Memory usage was still back to 150 MiB after opening and closing about 300 tabs in total, at which point I stopped.

The results of the different scenarios are reproducible every time (for me). I haven't tested NS 2.6.8.6 with all extensions disabled because it already works fine with everything enabled.

Edit: I just found the development versions and tried 2.6.8.7rc3 and rc4.
- 2.6.8.7rc3 behaves the same as in scenario C (aka. fine).
- 2.6.8.7rc4 behaves the same as in scenarios A and B (aka. affected).

Well, that release was performance-related - although ironically it was actually fixing a performance regression.

So... it doesn't look like NS 2.6.8.14 addressed the issue. Do you need any other information from me to debug this?

Edit 2015-02-24:
Nvm. This is obviously not going to get fixed. I'm a bit disappointed to see that NS is still shown as being compatible with FF 3.0.9+ on AMO, though.

ometa wrote:So... it doesn't look like NS 2.6.8.14 addressed the issue. Do you need any other information from me to debug this?

No thank you, I'm investigating it but had higher priority bugs to tackle until now.