InformAction Forums

Hi!

I am using Firefox 3.6.13 with latest Noscript 2.0.9.6.

Reproduceable, when http://www.n-tv.de is disallowed to use scripts, any click to reach a subpage of that site causes a complete freeze of firefox.

As soon as the site is allowed for scripts or noscript is completely disabled, the effect is gone.

The site starts to load and the title is shown by Firefox, but no page content. Due to the complete freeze, there are no logs.

Regards,

Can't reproduce on Firefox 4.

The site works fine for me here with NoScript's default settings and using no other extensions. http://www.n-tv.de is not allowed.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
NoScript 2.0.9.7rc4

Update NoScript to the most recent development build at http://noscript.net/getit#devel, then try these steps, in order, until NoScript is working right again.

- If you have any Firefox extensions called HP Smart Web Printing, Skype, .NET Framework Assistant, or McAfee Site Advisor, then uninstall or disable them. They're buggy and known to cause problems with the status bar icon.

- The NoScript settings became messed up somehow. Reset the NoScript Options by pressing Reset at the bottom of the Options dialog. Export your whitelist before doing that if you've added any trusted or untrusted sites you'd like to restore after NoScript is working again.

- There might be an extension conflict. Use the Add-ons manager to temporarily disable any other Firefox extensions you have installed, except for NoScript.

- Perform a Standard Diagnostic. If NoScript isn't working by the time you get to the "Create a new profile" step, a new profile with no other extensions besides NoScript should work right.

Hope this helps. Please let us know whether it does.

Hi and thanks for the hints to track down the problem.

Deinstalling the .NET Framework Assistant or exporting, reseting and reimporting the settings did not solve the problem.

The disabling of all other add-ons and step-by-step reenabling showed the reason.

It seems to be a conflict with "Google sharing 0.20", an add-on to route (and anonymize) access to Google services.

The problem can be reproduced here (with the current release and the latest dev-build). As far as I see, the problem does not come up, if the page is already in the local cache (when it was accessed before while Google sharing was disabled).

Regards,

Thank you for reporting your test results.