InformAction Forums

Hi guys I've been experiencing hangs since the 20110509 x64 build of Nightly. 20110424 was the last version before that that was working for me due to Bug 652747.

The problem is that consistently I've been seeing the browser hang up after 20minutes or more. In the bug that I filed at Mozilla's Bugzilla (https://bugzilla.mozilla.org/show_bug.cgi?id=655957) I mentioned a few sites but eventually it will happen on any site as far as I can tell. Even on Mozillazine's forum.

First I thought it was a Fx issue with Flash since that seemed to be the only correlation I could think of but after some extensive and annoying testing I've successfully identified NoScript as the "cause". Since it's working with older versions of Nightly without any problems I guess some checkin on mozilla-central in those 15 days caused NoScript to behave erratically. Unfortunately I can't further investigate the issue due to Bug 652747 but I thought I'd mention it anyway. The bug I filed on Mozilla's Bugzilla also contains some WinDbg64 stacktraces if those are any help at all.

Hope you guys can find a solution

Found-ish ... NoScript 2.1.0.4rc5 + Nightly 6.0a1 = hang at newegg.com

I already read that thread and I don't think it's the same thing. The work around that was proposed doesn't work for me since I don't have that entry in about:config that was mentioned. So I am guessing that the problem is unrelated. And if it is related the the work around doesn't work.

Edit: Unless I'm supposed to create that surrogate entry. I didn't think that was what was proposed but I could be misinterpreting what I've read.

I am experiencing the same problem, so I am going to ask you one question, if the answer is yes, there is your dilemma and if no, then we are in the same boat but with different problems. Have you installed the x64 prototype flash player (preview 3 at the moment) on that machine? or are you using the lame 32 bit workaround? If you are using the x64 flash, the problem is how nightly and that don't play nice when a website using somewhat obsolete references in their flash code can trigger an infinite loop, hence the hang, I suffer from it ALL THE DAMN TIME. If you are not using the x64 flash in conjunction, then I am afraid that we are facing a dilemma that I can't assist you with, at least not at this precise moment without further debugging which has been a nightmare. BTW, not ruling it out, but as far as I can see, NoScript is not doing anything wrong here, but we'll have to see.

Andu wrote:Edit: Unless I'm supposed to create that surrogate entry.

No, it should be there by default (if it's not, it's an oddity of its own).

noscript.ABE.disabledRulesetNames;SYSTEM
noscript.ABE.migration;1
noscript.gtemp;
noscript.options.tabSelectedIndexes;5,4,0
noscript.policynames;
noscript.subscription.lastCheck;-502885851
noscript.temp;
noscript.version;2.1.0.4rc5
noscript.visibleUIChecked;true

These are the only noscript related entries I have. The weird thing is this profile is relatively fresh. Maybe 3 weeks old.

Andu wrote:noscript.ABE.disabledRulesetNames;SYSTEM
noscript.ABE.migration;1
noscript.gtemp;
noscript.options.tabSelectedIndexes;5,4,0
noscript.policynames;
noscript.subscription.lastCheck;-502885851
noscript.temp;
noscript.version;2.1.0.4rc5
noscript.visibleUIChecked;true

These are the only noscript related entries I have. The weird thing is this profile is relatively fresh. Maybe 3 weeks old.

Mmm, I'm pretty sure you're sorting by "modified", i.e. you've got all the modified (bold) entries on top. Try to sort by name and check again.

("Status" it seems to be for me. Neat. Never even knew you could do that.)

Giorgio Maone wrote:

Andu wrote:noscript.ABE.disabledRulesetNames;SYSTEM
noscript.ABE.migration;1
noscript.gtemp;
noscript.options.tabSelectedIndexes;5,4,0
noscript.policynames;
noscript.subscription.lastCheck;-502885851
noscript.temp;
noscript.version;2.1.0.4rc5
noscript.visibleUIChecked;true

These are the only noscript related entries I have. The weird thing is this profile is relatively fresh. Maybe 3 weeks old.

Mmm, I'm pretty sure you're sorting by "modified", i.e. you've got all the modified (bold) entries on top. Try to sort by name and check again.

Actually it is sorted by name and I used the filter on the keyword 'noscript'. But I just checked it again without using a filter and no change there ~~

Andu wrote: Actually it is sorted by name and I used the filter on the keyword 'noscript'. But I just checked it again without using a filter and no change there ~~

Very very strange then: aren't they all in bold (i.e. only the non-default prefs)?

Yes they are all bold.

Andu wrote:Yes they are all bold.

And when you don't apply any filter, are the bold entries all grouped together?

No, they are not. May I ask why we are going over these details again and again?

Edit: Maybe I should add that I've been using nightly builds and about:config since back in the Fx 2.0 or Fx 1.5 days. So unless I make a mistake I'm usually not entirely clueless about what I'm doing.

Andu wrote:No, they are not. May I ask why we are going over these details again and again?

Because if you're 100% sure they're the only noscript.* entries in your about:config, you've got serious problems with your profile as all the default NoScript preference entries (and they're a lot) are missing, which may or not may have to do with the problem at hand but surely is a big anomaly which makes impossible to tell where the problem actually is.

Filtering on 'noscript' (not that it's readable, but ...)