
The peaks are Firefox using 100% of one CPU core, and it is during that time that it hangs. Needless to say, it is unusable in this condition which forces me not to use NoScript 2.
EDIT: Image extended to show private bytes history as well.
miroslav.policki wrote:The peaks are Firefox using 100% of one CPU core
1. The resolution is 6 seconds (perhaps +-5%) per square. The screenshot is from Process Explorer.Giorgio Maone wrote:
- What' the time resolution of that graph (i.e. how often does the peak happen and how long does it last)?
- Does downgrading to 1.10 actually help?
- Does disabling the new WAN IP protection in 2.0 help?
- Have you got any security software (especially personal firewall or "web shield") which installs a browser plugin? If so, could you try disabling it and/or check for errors in its logs?
I've got Comodo and used to have Avast (I'm using Comodo's antivirus as well now to reduce the clutter) and as far as I can recall Avast has some sort of transparent proxy used to provide "web security".miroslav.policki wrote: 4. I use Comodo Firewall and Avast antivirus but neither of them have installed plugins. Besides, as I first reported, all plugins and extensions except NoScript were disabled during the observed behavior.
In particular, Avast calls it the Web Shield. Unfortunately, temporarily disabling the Web Shield in Avast's REAL-TIME SHIELDS > Web Shield pane does not disable its transparent proxy. Temporarily disabling it merely tells the proxy not to do any malware checks while its handling each packet.Giorgio Maone wrote:as far as I can recall Avast has some sort of transparent proxy used to provide "web security".
Could you try temporarily disabling it and see if it makes any difference?