Another script error and instability of Firefox with Zotero 2.0.2

lufiend

Since upgrading to Zotero 2.0.2, Firefox has suddenly become extremely unstable on my computer (Windows XP, Firefox 3.6). Firefox freezes, sometimes irremediably so that I have to force a shutdown via the task manager (CTRL-ALT DEL). Using Zotero functions (working with my library) almost always trigger temporary or permanent freezes. Sometimes I get script error warnings, though not necessarily the same as in other threads. The script error reads:

Script: chrome://zotero/content/xpcom/attachments.js:1087

Despite the freezes, Firefox does not appear to be taking up any extra CPU or memory during the episodes (I have monitored my computer's resources during these events).

Firefox has become so unstable that I hardly dare use it anymore--I am posting this message using Google Chrome!

dstillman

Try disabling auto-sync in the Sync pane of the preferences.

If you're getting a warning there, it would likely be during sync, and it would be disk activity, not CPU.

Right-click, Properties on the 'storage' directory within your Zotero data directory. How many folders and files?

dstillman

Also, just to be clear, that's not really an error, and clicking "Stop Script" is almost never the right thing to do.

http://www.zotero.org/support/kb/unresponsive_script_warning

lufiend

37,934 files, 297 folders.

That seems like a lot of stuff.

dstillman

Have you clicked Continue and let it complete?

lufiend

It does look like the sync is what is causing this. I had no problems at all while no syncing was in progress (I deactivated the auto-sync). But when I performed a manual sync, Firefox immediately froze up and also repeatedly returned the above-mentioned script error. After several tries, I was forced to choose "stop script." After choosing stop script, Firefox stabilized, it has to be said.

lufiend

And, yes, I tried to have the script continue but it never completes. After several runs, I finally clicked the evil "Stop Script" button.

dstillman

This isn't a question of stability. It's processing. (Reread the linked page for an explanation of what the message means.) The next time you're going to be away from your computer for a while, set dom.max_chrome_script_run_time to 0 (as explained on that page) and start a sync. Unless there's actually a problem with a particular directory, which is unlikely, it should eventually complete.

Once the large initial sync goes through, you shouldn't have this problem again.

dstillman

You can also provide a Debug ID for the sync attempt, which would provide us with a bit more information.

lufiend

I would hate to doubt the words of someone who has much more knowledge of computers than I (I am no geek, just a consumer of software), but there is one thought nagging at the back of my head: I was a Zotero 2.0 Beta user and have been for a few months. My Zotero library has long been synched with my online account. Why would there be a "large initial sync" at this moment? I have already done that. These are small update syncs. I have read your link to "unresponsive script warnings" and I understand the basic point of it. I just have this idea that that is not what is going on. I'll stick to your advice and see where it gets me.

dstillman

OK, I wasn't aware that you had been syncing previously.

There are still a number of things that could cause Zotero to process files again, but we'd need a Debug ID to know exactly what was going on. You can do this before changing the run time setting.

lufiend

Here it is:

The Debug ID is D2035413600.

dstillman

OK, so a couple things:

1) You're hitting a file sync quota (on a 100MB file), and you should see a message saying such. So no new files are being uploaded, and each time you sync it's trying to include all the files since the last time you successfully synced. Currently that's 202 files. So it's not actually a "small update sync".

2) Your files are taking a very long time to process. Is this an old computer? Is something else using the disk at the same time? Have you tried restarting?

First, if you don't mind, install the trunk XPI. I've made a small change that might improve responsiveness in the place you're hitting. Despite the warnings on that page, it should be perfectly safe to install the dev build, as this is the only change since 2.0.2 (except for one other that only applied to the upgrade process). You can switch back to 2.0.2 after seeing if the patch helps.

Second, you should either buy more storage or simply disable file syncing in the Sync pane of the Zotero preferences.

For a future release, we'll try to adjust Zotero to not attempt keep trying a file sync after a quota error until the next manual sync is performed.

lufiend

Here are my answers:

1. It's not an old computer. It was custom built for me a little under a year ago. It has a triple core processor (AMD Phenom II X3 720 2.81 Ghz, 3.25 GB of RAM) and usually nothing is running in the background, or perhaps small programs.

2. I only once got an error message about a file sync quota (I can't remember when or what file). I did not get this message this time around. I would like to know what file of 100 MB I put into Zotero that is messing things up. I don't usually put large PDFs like that into Zotero.

3. I have installed the trunk XPI in a separate Firefox profile. When I tried to start Firefox after that action, I got the script error js:244 listed elsewhere on this forum when starting up. I have run a Debug after restart: the Debug ID is D1224162475. Would it make sense to try and use the trunk XPI for my main profile as well?

lufiend

After installing the trunk XPI in my main profile, I get

Script: chrome://zotero/content/xpcom/data/item.js:2612
Script: chrome://zotero/content/xpcom/attachments.js:1087

during syncing.

dstillman

I did not get this message this time around.

You don't see an error to the left of the sync icon when you sync?

When I tried to start Firefox after that action, I got the script error js:244 listed elsewhere on this forum when starting up. I have run a Debug after restart

And that Debug ID is for a startup that showed the error?

What's your dom.max_chrome_script_run_time value in that separate profile?

Would it make sense to try and use the trunk XPI for my main profile as well?

Yes. The translate.js:244 message is unrelated.

lufiend

>>You don't see an error to the left of the sync icon when you sync?

I did when I last ran it again and had the sync complete (in my MAIN profile). Sorry about misunderstanding your comment. I didn't realize you meant the maximum file storage quota.

>>And that Debug ID is for a startup that showed the error?

Yes.

>>What's your dom.max_chrome_script_run_time value in that separate profile?

20

dstillman

OK, I'm not sure why you'd be getting these warnings on a fast computer unless something else on your system is conflicting, but my original advice for the sync issue still applies: buy more storage or disable file sync.

And try setting max_chrome_script_run_time to 60. If you then get freezing with file sync disabled (or after purchasing more storage and letting it sync), we can take another look.

dstillman

Also, after setting that to 60 (or simply 0), if a particular action is slower than you expect it to be, provide a Debug ID. Debug output includes timings that let us see how long things take, but they're thrown off by the alerts.