noscript causing firefox to crash

[edrick]

A number of people are having issues with noscript causing firefox to crash while browsing at www.neogaf.com. It just started happening yesterday. Any ideas what the problem may be?

[Giorgio Maone]

Could you paste links to your latest about:crashes entries? (type "about:crashes" inside your address bar, hit [Enter] and select/coot the top report IDs).

[edrick]

The crash happens with firefox 6.02 and 7.

https://crash-stats.mozilla.com/report/ ... d492110914
https://crash-stats.mozilla.com/report/ ... 2a22110914
https://crash-stats.mozilla.com/report/ ... 6b02110913
https://crash-stats.mozilla.com/report/ ... 30e2110913

[therube]

That points to (mainly with) AVG 10.0.
And so does the second report.
Do you have AVG installed on your computer?
Do you have its browser plugin component running?

Disable it & see if your crashes continue.

The third looks like something with nVidia (drivers?) & Flash.
The fourth looks like a Flash crash.

Don't see where people are complaining of NoScript related crashes on that board, http://www.google.com/cse?q=noscript+cr ... ISO-8859-1. Crashes in general, perhaps. (And even then, the posts don't have dates, or did I miss that?)

[edrick]

I do not use AVG.

Here's a few people discussing it on the forum: http://www.neogaf.com/forum/showthread. ... 158&page=3

[therube]

Any other A/V with plugin, or other odd plugin?
(Check about:plugins & also Add-ons Manager.)

Do your crashes subside if you disable NoScript?

[edrick]

Any other A/V with plugin, or other odd plugin?
(Check about:plugins & also Add-ons Manager.)

Do your crashes subside if you disable NoScript?

I do not use an a/v. and yes if I disable noscript, the crashes stop.

[Giorgio Maone]

Is it just "while browsing" or is there any sequence to reliable reproduce it?
Must I be logged in?
What permissions need to be granted?

[edrick]

Is it just "while browsing" or is there any sequence to reliable reproduce it?
Must I be logged in?
What permissions need to be granted?

It happens while browsing the forum. The site will attempt to load, but it will hang before the page is fully loaded and then firefox will crash.

I just tested to see if the crashes happen while logged out, and they do still happen. While trying to open up new threads in tabs I noticed that the tab loading icon will freeze for a few seconds and either finishing loading or crash firefox.

[edrick]

The crashing has stopped today. No idea why.

[therube]

Did FF update, as in are your now running a more recent build?

(Gee, glad we can tell that from the UA! FF, idiots IMO.)

[edrick]

Nope, FF has not updated. Someone thinks that the crashing was related to stats.big-boards.com, being very slow or down the past couple of days.

[dhouwn]

Just had the crash in rapid succession, first my Aurora crashed, then Firefox beta. Neither I use AVG or something like that.
Many of the crash reporters seemed to have NoScript installed, so I am now pretty confident that it is something triggered by NoScript.

[therube]

> Many of the crash reporters seemed to have NoScript installed

Given its popularity, is that unexpected?

And what makes you think it is NoScript related?

Crash report #'s?

Earlier SeaMonkey aurora/betas were wholly unstable for me.
Current release candidate has been fine. (Last few candidates actually.)
Now what does that prove - nothing.

Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110916 Firefox/7.0 SeaMonkey/2.4

[GµårÐïåñ]

@therube, I am not saying necessarily that NS is involved. But the reason the assumption is made and is often a legitimate assumption, is when you have the same things across the board and they work find and suddenly they are start doing something and have ONE thing in common, otherwise different, what would you think is the problem? Common sense, really, I know from a non tech perspective it seems a rush to judgement but its often a legitimate assumption to begin with. Although another common issue could be the core (mozilla/gecko foundation) that is common and can have gone to hell too, but usually different builds without updates to something new (meaning something didn't change) should not be the sudden cause.