InformAction Forums

For weeks now I have rather continuously received an error that will not only cause my Firefox to crash, but sometimes freeze my entire PC to the point of needing a manual shutdown.

chrome://noscript/content/ioutil.js:59

I will get this error, accompanied by a message that says something to the effect of "A script is having a problem, do you want to stop it or let it try to finish loading?" and then has a "Don't ask me this again" check box.

Every time I click the "stop" with the check box marked, yet I continuously get this error.

I get the latest NoScript every time it comes out, and last I knew I had the latest Firefox that wasn't Firefox 4.

This is really irritating. A Google search has yielded me very little in the way of any results.

Please help, this is getting really, really, really irritating.

I searched your forums and didn't find anything related to this, so...yeah. Thanks in advance...

This is very likely an extensions conflict.
Could you try Standard Diagnostic keeping NoScript enabled?

I have the exact same problem. Per the suggestion, I tried clicking on the link to run a diagnostic. However, the site would not come up and I got time out errors. Possibly my computer is so clogged with the problem that it causes the connections to time out. Sort of a Catch-22.

On another forum that I found by searching, I saw suggestions to go to Tools within Firefox and then to Add-ons and the Extensions and to disable items. This was consistent with the suggestion above so I tried that and restarted Firefox.

That apparently fixed the problem (or else some clog in the startup pipeline coincidentally finally cleared itself)

Most people on the other forum had Skype or Adobe extensions that were apparently the problem. In my case I noticed that I had three Java consoles running, so I disabled all but the most recent version.

A very simple fix if it works. Hope that helps someone else.

Montana Guy wrote: Most people on the other forum had Skype or Adobe extensions that were apparently the problem. In my case I noticed that I had three Java consoles running, so I disabled all but the most recent version.

A very simple fix if it works. Hope that helps someone else.

Thanks for sharing.