Unresponsive Script

[zupp]

I got this error about three times in the last 4 days: Script: chrome://flashgot/content/XPCOM.js:74.
The whole computer freezes and it takes about 10-15 mins before things start working. Then is when FF shows this error and clicking Stop I guess fixes it (I haven't clicked Continue so I can't be sure what that does).
The other time I got this the error might have been different or not even flashgot related. But I copied the error message this time.

[therube]

The whole computer freezes, & not just FF?
Is Namoroka new for you (did you install it 4 days ago too)? (Based on the build date, could be.)
What version of FlashGot are you running?

[zupp]

The computer freezes to the point where only the mouse moves but any action (such as trying to open TaskManager or clicking a desktop item) takes ages. Explorer.exe doesnt stop so the issue is something else.

Namoroko isn't all that new to me, I have been using the nightlies for quite a while now and as soon as Namoroka was available as an official nightly upgrade that's when I got it. Whether that was 4 days ago I can't be sure.

FG 1.2.0.2

[Giorgio Maone]

The weirdest thing is that line 74 of XPCOM.js in FlashGot 1.2.0.2 is empty...
IMO there's something severely broken in your profile (I'm testing FlashGot in Minefield and works like a charm).
Could you check if it works on a clean profile, and if this is the case try
http://kb.mozillazine.org/Transferring_ ... ew_profile ?

[zupp]

Giorgio the thing is this issue isn't repetitive enough to declare it over or not. Infact since starting this thread, I haven't had this problem even once. But still, I've had alot of flashgot-like add-ons previously and Ive not cleaned the prefs file. Maybe I should have tried that before I posted here.
I will surely update you guys as soon as this problem shows up again. Thanks for your replies and help Giorgio and therube.

[GµårÐïåñ]

I have been getting this too and it has been hanging on Netflix and also on local FEBE extension's backup process. Before this was happening and I extended dom.max_script_run_time and dom.max_chrome_script_run_time to a large number and eventually the problem went away but it has come around again but the only reason I haven't mentioned is because I cannot pin point with which version it came but it has. I have checked and even made the wait time longer (unreasonably frankly) but still no fix. Something is stalling scripts, it happens on websites AND extensions. Now I have both NS and FG, so not sure which one is the culprit, my money would be on NS but just thinking out loud.