[INVALID] NoScript + 3rd party site JS content == FF hang

[abjbhat]

Ok, so I'd noticed this a while back and it went away..but now its back again. I'm using FF 19 + NoScript 2.6.4.4. When a 3rd party JS tries to load - sometimes, but not always - Firefox completely stops responding. Now, this isn't a "Firefox isn't responding"; Firefox just stops painting or doing anything. The screen gets stuck, no mouse clicks, keyboard input, no nothing works anymore. I can of course kill the Firefox process via the task manager.

So here are some examples.

Facebook + scripts from akamaihd.net == hang
Gmail + scripts from googleusercontent.com == hang

The browser loads the scripts from the 3rd party site, and then nearly at the end of the load... nothing. The browser just stops. It stops responding to any input whatsoever. In task manager, it shows Firefox as working fine, i.e. The "Firefox isn't responding ..." message doesn't come up.

This behaviour isn't reproducible consistently with other 3rd party/cdn hosted scripts, but is always reproducible with the above two examples. I've switched off ABE rules, other plugins, reset my whitelist, but nothing works.

Please help!

[therube]

If you disable NoScript, do the hangs persist at those same sites?

[abjbhat]

Yes, that correct. If I disable NoScript, the two pages I've mentioned load correctly.

[therube]

And on those two sites, what particular domains do you have Allowed?

[Mist]

Fire Fox 18.0.2
NoScript 2.6.4.4

I think I'm having the same problem.

All has been working like clockwork until about three days ago.

I click a site, click the NoScript "S", in my case in the lower right, to allow the site particulars (different depending on site), and everything freezes. No mouse, can't exit except via Task Manager when I get my mouse back - frozen hang.

Initially, I thought it might be within Fire Fox due to a Java script problem I'm fighting. I was at an Australian news site a few moments ago and by accident think I discovered the problem. I clicked No Script and received the familiar frozen hang. Waited for it to clear, clicked out. All is well again.

Okay, folks, whatever it was that you changed, change it back. Please.

Thanks.

[Giorgio Maone]

Fire Fox 18.0.2
NoScript 2.6.4.4
[...]
All has been working like clockwork until about three days ago.
[...]
Okay, folks, whatever it was that you changed, change it back. Please.

Nothing, absolutely nothing changed since January the 29th (when 2.6.4.4 has been released).
Did you install any new software / add-on in the meanwhile?

[Mist]

Nothing, absolutely nothing changed since January the 29th (when 2.6.4.4 has been released).
Did you install any new software / add-on in the meanwhile?

Aside from Fire Fox extension updates, I Installed two extensions since removed so I would think they wouldn't be a factor.
I removed Fire Fox extension Wire something since I don't need it any longer.
I also removed totally Fire Fox and reinstalled a freshly downloaded 18.02.

Only other changes are my usual reading lists updates, news, journals, etc. I've been using for the past decade plus.

[Giorgio Maone]

I also removed totally Fire Fox and reinstalled a freshly downloaded 18.02.

Could you check whether the problem persists on a clean (new) profile with just NoScript installed?

[Mist]

I also removed totally Fire Fox and reinstalled a freshly downloaded 18.02.

Could you check whether the problem persists on a clean (new) profile with just NoScript installed?

Think I can do that.
What I forgot to mention, OS is Windows 8. My apologies. Not sure if that's a factor or not.

[abjbhat]

Yeah, that's the same with me - Win8 x64

[Mist]

Problem persisted.

Switched to Chrome without NoScript (yet) and all works well.

Subject: ISC StormCast for Friday, February 15th 2013
http://isc.sans.edu/podcastdetail.html?id=3127, (Fri, Feb 15th)

Not a blurb but if you don't get the audio in either Flash or HTML5 something is wrong.

I see that my NoScript was automatically updated. No change.

Unable to get a response from Mozilla.

[Mist]

Thanks for your help, Mr. Maone.

Sorry to have been a bother but I believe the problem is in either Mozilla or Java, not NoScript from my results from trial and error.

All the best,
E. Bartley