"Unresponsive script" post thread

[southdave]

[cbaker_admin]

Also try running "Verify extension directory" in Tools > FEBE > FEBE Options > Misc. There might be "leftovers" from the Fx upgrade.

[paulderdash]

I appear to have the same issue as Dave. The profile backup does appear to have been created but the program window keeps running. If I abort I get the attached message:
Script: chrome://febe/content/febeZip.js:107 (stopped responding or busy ...).
On restart FEBE reminds me to backup so does not recognise the backup it has (I think) created ...
I have tried verifying extensions - and did in fact get an error which I allowed FEBE to fix.
Like Dave, this extension has saved me on several occasions ...

Rgds - Paul

[imeiou]

I have the same issue as well:

Script: chrome://febe/content/febeZip.js:62

Everything was just fine on FF 3.5.7. Upgrade to 3.6 broke it.

BTW, backup appears to have been created, but, upon close inspection, you realize it's a PARTIAL file. Its like it hung less than halfway through while adding extensions.

The check extensions feature lists this error:

***multifox@hultmann is not a valid GUID.***

I let FEBE remove it. No errors are reported anymore. And it still hangs just like before.

[cbaker_admin]

I upgraded to Fx 3.6 yesterday and got a similar message when the scheduled backup performed this morning. I clicked "Continue" and the backup did complete. I have performed several manual backups since then and they all work fine (without the "Script is busy message").

You mention that you think your backup is partial. Are you getting a Results Report? FEBE does not generate that report unless the backup does indeed complete without errors (except those errors that are trapped and mentioned on the report). Try comparing a previous report with the current one to see if they are the same, more or less.

[Norky]

I am in the same boat after upgrading to FF 3.6.
I have run the verify extension directory and found no problems

The unresponsive script error I get is:Script: chrome://febe/content/febeZip.js:62

[imeiou]

I mention partial, because after not letting the script continue (since it's not even consuming CPU, I assume it's just hung, deadlocked or smth), because the generated file is 1/6 the size of previous backups. And upon opening it, I see that it doesn't have everything in there (I'm performing full backups).

Also, the first time I saw the progress window hung this morning, it was about 7AM. FEBE is scheduled for 3AM. It had been there for a long time.

[cbaker_admin]

Ok, I'd like to ask everyone for some help debugging this. Please install and run a backup. It will create a log of the items it is zipping. Depending on where the error is occurring, the log will display either the last backed up item or the item currently being backed up.

If you could would post the last item in the log, maybe we can figure out a common denominator. It would also be helpful if you can figure out what the next item on the log would be. I'm not even sure this is possible, but by looking in your directory you might be able to find which entry comes after the last one in the log.

[imeiou]

Mine showed these last 3 lines:

\Users\<removed>\AppData\Roaming\Mozilla\Firefox\Profiles\<removed>\extensions\greasefire@skrul.com\indexes
\Users\<removed>\AppData\Roaming\Mozilla\Firefox\Profiles\<removed>\extensions\greasefire@skrul.com\indexes\exclude.dat
\Users\<removed>\AppData\Roaming\Mozilla\Firefox\Profiles\<removed>\extensions\greasefire@skrul.com\indexes\include.dat

I guess the next files would be

info.ini
scripts.db

that sit on that same dir.

I then uninstalled Greasemonkey and Greasefire to see what would happen.

The progress window was still sitting still. Moving it around will show the standard firefox window for a script that is taking too long. Clicking continue on that window will finish things up. But, only manually clicking it. If I don't, things won't finish up by itself. Taking away all scheduled automation from the process.

[Norky]

[cbaker_admin]

In aboug:config there is a preference called dom.max_chrome_script_run_time that controls how long Fx waits before giving the "Script is busy" message. The default value is 20 seconds. Let's try changing it to "60" to see if that will eliminate the problem.

Fx 3.6 is supposed to be much faster than 3.5.7, but maybe some things (like nsIZipWriter - the XPCOM component FEBE uses) are actually taking longer than before.

[imeiou]

That must be a magic number...

I did try changing that same configuration earlier. I was googling around and stumbled upon that. I changed it to 40. Didn't solve anything.

Then I came in here to check what ppl would be saying. I saw you mentioning it. Then I thought to myself... heck... let's balloon it up to 60, what do I have to lose? 60 solved it... lol ... I thought I would just stand here and see the progress window. Nope. Solved it.

It was really Fx getting in the way and HALTING the script until I let it continue.

[Norky]

[cbaker_admin]

Not that I would suggest it, but you can set that preference to "0" (zero) and Fx will never time out.

You can go back to FEBE 6.3.2 by installing it from either the or .

[Norky]