Zotero freezes as soon as it's opened - impossible to use
Hi,
I am an owner of a group library and also an admin of another. One of the other admins for the 2nd library I mentioned is having real problems even getting Zotero to launch in Firefox. It opens, the sync icon starts to move and then it freezes and we have to quit firefox. I, and other group members, don't have these same issues. We are all in the same office and work on a Cloud IT system.
Before Zotero crashes, I can see that there are lots of 'open circles' in her version of the library and nothing has been added for the last 12 days (although other users can see these recent items in their libraries).
I tied the Standalone version, which imported setting from the web version and asked for her password, but then constantly frize just like the Forefox version.
Any help?! It's currently impossible for her to use.
Thanks,
Ali
I am an owner of a group library and also an admin of another. One of the other admins for the 2nd library I mentioned is having real problems even getting Zotero to launch in Firefox. It opens, the sync icon starts to move and then it freezes and we have to quit firefox. I, and other group members, don't have these same issues. We are all in the same office and work on a Cloud IT system.
Before Zotero crashes, I can see that there are lots of 'open circles' in her version of the library and nothing has been added for the last 12 days (although other users can see these recent items in their libraries).
I tied the Standalone version, which imported setting from the web version and asked for her password, but then constantly frize just like the Forefox version.
Any help?! It's currently impossible for her to use.
Thanks,
Ali
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
If the issue is the latter, Zotero may just be trying to handle a large sync and you're not giving it enough time. If you haven't already, let it run for at least 30mins when it's frozen, clicking "continue" if you get an unresponsive script message.
If this is indeed a crash, we'll need to troubleshoot this with the person on the computer directly.