[RESOLVED] 1.9.8 causing browser to get stuck on some sites

[raekwon00]

Ever since updating from NS 1.9.7.9 to 1.9.8, Firefox has been getting "stuck" for me while loading meebo.com. Nothing is clickable, and eventually I have to Force Quit the browser and restart.

Rolling back to 1.9.7.9 has resolved this, so there seems to be something in 1.9.8 that's causing this.

[Giorgio Maone]

Does it happen on a specific page of meebo.com which I can look at?
Could you try setting the dom.max_chrome_script_run_time about:config preference to 10 and check if any error message pops up after 10 secs of "hang"?

[random user]

I upgraded to NS 1.9.8. After doing so, I could not use Firefox. My homepage is the New York Times. The browser would hang trying to load it. Opening another tab wouldn't often help. Firefox became non-responsive (clicking on anything didn't produce a response or a *very* delayed response). I also noted that the address bar was incorrectly displayed. Rather than having a white background it is gray like the surrounding. On removing NS, everything was fine.

[Giorgio Maone]

I upgraded to NS 1.9.8. After doing so, I could not use Firefox. My homepage is the New York Times. The browser would hang trying to load it. Opening another tab wouldn't often help. Firefox became non-responsive (clicking on anything didn't produce a response or a *very* delayed response).

As I asked the previous poster, could you try setting the dom.max_chrome_script_run_time about:config preference to 10 and check if any error message pops up after 10 secs non-responsiveness?

I also noted that the address bar was incorrectly displayed. Rather than having a white background it is gray like the surrounding.

That's very stange, and hinting at an extensions conflict. Does this problem persist after disabling all the extensions except NoScript from Tools|Add-ons?
If it doesn't, could you try Standard Diagnostic?

[random user]

As I asked the previous poster, could you try setting the dom.max_chrome_script_run_time about:config preference to 10 and check if any error message pops up after 10 secs non-responsiveness?

It is difficult for me to alter the NoScript preferences since FireFox is non-responsive. I imagine there is a file somewhere that I can edit. What is it called?

[Alan Baxter]

Restart Firefox in Firefox safe mode http://support.mozilla.com/en-US/kb/Saf ... =safe+mode
Edit the preference while in safe mode. While you're at it, change when Firefox starts to "Show a blank page" in the Firefox preferences Main panel.

[random user]

I did as you asked and changed dom.max_chrome_script_run_time to 10 (changed home page, reloaded NS, etc). No error message popped up but Firefox was unusable after I went to the New York Times page.

[Giorgio Maone]

@random user:
does it happen also on a clean profile?
Is it the NYT home page ( http://www.nytimes.com/ ) or some specific inner page?
Does the problem persist even if you use NoScript Options|Reset and/or Allow scripts globally?

[RandomGuy]

Hi.
The dom setting let the browser load more of the site but also stucks
It happens on most sites with shockwave flash plugins.
I use OSX 10.5.8 and ff 3.5.2.
All i can say is that http_connections went into close_wait which seems to be severy for the browser.
close_wait should not happen so i think this is a severe bug. (perhaps close($socket) forgotten ?).
Deactivation 1.9.8 works. I deactivated all plugins except noscript.
ALso possible is a flash coexistance problem. In my dtrusses i see that the flash plugins loads but something wann break the socket which is not allowed in this state:
296/0x7f3f048: recvfrom_nocancel(0x11, 0xB0102C2F, 0x1) = -1 Err#35
Could it be that noscript examines the socket trough a pipe or something ?
The flash plugin opens up a socket (eg. myspace) and then wants to connect to the dest via http proto.
Then noscript scans the content and then ?
After the error orrurs all socket sonnections go into close_wait.
DNS resolving isn't possible anymore. All recvfroms (udp) termintated with ERR 35.
So, perhaps that could be a hint to begin to debug the prob.
Randy

[Giorgio Maone]

@RandomGuy:
Looking at the signatures in this thread it starts to shape up as a Mac OS X-specific Firefox bug triggered by NoScript.
Since the most low-level networking code in NoScript is the ABE module, could you try to disable it from NoScript Options|Advanced|ABE and check if the problem persists?
I'm testing on Mac OS X at this moment, since it's completely unreproducible on other platforms, and maybe I'm on something...

[RandomGuy]

Hi,
If i disable ABE in the settings it works again.
What drawbacks should i expect when deactivating ABE ?
Randy

[Giorgio Maone]

If i disable ABE in the settings it works again.
What drawbacks should i expect when deactivating ABE ?

Currently you loose the default protection against cross-zone (web to LAN) CSRF attacks.
In future web applications may opt in for CSRF protection, but I hope to fix this issue within 24 hours.
More info here: http://noscript.net/abe

[dbfinch]

Just thought I'd drop by and report that I'm having the same sort of issues since upgrading to 1.9.8. Was having trouble browsing a vB forum earlier, sites such as MySpace, Facebook and TSN.ca were causing FF to come to a halt. I'd initially thought it was a FF issue so cleared the cache and browsed history, but that made no difference, and when Safari worked OK on the same sites I figured it was one of the add-ons. Turned NS off and the problems went away, back on and they came back. I too have now downgraded to 1.9.7.9 and everything is OK, I did try the about:config suggestion but it made little difference. Oh and yes, I too am OSX 10.5.8.

[Giorgio Maone]

Thank you all for reporting.
It's confirmed as a Mac OS X specific issue, and therefore I disabled the compatibility flag on AMO until this gets resolved, in order to prevent other users from being automatically upgraded.
As I said, I hope to release a fix within 24 hours.

[Giorgio Maone]

@everybody:
please check if latest development build 1.9.8.1 fixes this issue as I hope.
Don't forget to turn on ABE and restarting the browser before testing.