[RESOLVED] FYI- newest version hung FF

[pmcwillie]

Yesterday I clicked approval to update NoScript. Immediately after installing it, FF (3.5.9) would hang after moving the window. Only way to free it was to hit the WINDOWS key a few times ?!?#?%

Thanks for posting the link to previous versions of NS, I installed 19957 & everything's find now...also updated FF to 363 w/ same outcome.

[Giorgio Maone]

Very likely an extensions conflict.
Does it happen on a clean profile w/ just NS?

[kosiam]

I'm similarly having problems with the latest update in FF 3.6.3. I recently created a new profile, and began restoring extensions using FEBE. So far the only things I restored (in order) were FEBE 6.3.2, XMarks 3.5.10, FastDial 2.23b1, AdBlockPlus 1.1.3, and NoScript 1.9.9.57. I had Task Manager>Processes running (Windows XP Home SP3) and did a browser restart with each installation. Upon restart with NS19957 I had noticeable lag, and FF mem usage jumped from 180MB to 300MB. When I disabled NS mem went back to 180MB and all was normal.

[Giorgio Maone]

@kosiam:

1. Could you retry with latest development build?
2. Should the problem persist, could you disable all the other extensions and enable them one by one (with NoScript present), in order to find the conflict?

[eikenberry]

Using firefox (iceweasel) 5.3.8 on Debian Linux with noscript 1.9.9.69 I also hit what seems like the same or a very similar issue.

On certain pages (example link below) when closing the tab, quiting or clicking a link the CPU and memory usage spike for a few seconds then a popup comes up with the title "Warning: Unresponsive script" with no content in the popup window. In a test profile I've removed every extension but noscript. It is running in pretty much the default setup as well.

http://www.amazon.com/Mighty-Bright-Xtr ... 099&sr=8-3

[eikenberry]

Using firefox (iceweasel) 5.3.8...

I obviously meant 3.5.8.

[eikenberry]

I tried a fresh profile (previously test was with copy of my current profile) with only noscript installed. It didn't exhibit the issue. I went through the options, duplicated the settings and still no issue.

So my current guess is that it is a conflict with some other extension that doesn't clean up after itself very well so I still get the issue even after uninstalling it.

I'm going to start a fresh profile and copy over my various settings, install all the extensions and see if that fixes it.

[GµårÐïåñ]

You might also consider deleting your extension reference files in the profile directory and then restart Fx so that it will rearrange them and recreate the index and sometimes it forces things in orders that will resolve the conflict, although not always and you have to click update when you start Fx for the first time after deleting those files to ensure that version corrections are noted and then it will ask for a restart and it SHOULD fix any problems you have. Give it a try and see. I have often had to do it SEVERAL times until the load order was such that problems went away, and I don't mean with NoScript, I mean in general. Good luck.

[eikenberry]

Which files exactly do you mean when you say "extension reference files"? In the profile's directory there are extensions/ (dir), extensions.cache, extensions.ini and extensions.rdf. In the [profile]/extensions/ directory there are the various dirs for the extensions as well as Extensions.rdf.

Thanks for the help.

[GµårÐïåñ]

It has been extensively discussed in the past and I have given instructions but I can't find the links to it, so here it goes again but I will use direct text from Mozilla this time to expedite it, ok?

Relevant Excerpt:

Corrupt extension files

It's possible that the files that store information about your installed extensions are corrupt, preventing you from updating or uninstalling an extension. To resolve this, close your Mozilla application and delete (or rename) the following three files from the profile folder (the files will be regenerated upon application restart):

* extensions.cache
* extensions.ini
* extensions.rdf

Direct Link:
http://kb.mozillazine.org/Uninstalling_ ... sion_files

Tip: Click Start -> Run... -> %appdata%
This will open up the appropriate folder in which you can locate Mozilla, then Profiles, and then find your specific profile (if only one, it will be called ####.default) and then the files are located there. Good luck.

[eikenberry]

Just as a wrap up of my issue. It was not an extensions conflict issue. Deleting and recreating the extensions references files did not help.

Turned out the problem was a relation between an old amazon cookie and noscript. I had gone through deleting all firefox's 'state' and when I got around to the cookie file that fixed it. So then, after restoring it, I deleted just the amazon cookies (the site where I was having the issue) and the problem went away. Re-logged into amazon (reacquiring the cookies) and still no problem.

[GµårÐïåñ]

I am glad that you figured out what it was and that you got it resolved, thank you for letting us know.