Latest update is unstable

sci6676
Following the latest update of Zotero it seems to have become very unstable and it takes rarely more than one two input actions to crash. For example when I try to add a new entry from a PDF as "stored copy of file" Zotero first freezs for a few seconds and then tells me that I have to restart (error report codes 1178093087 from Standalone version and 603332634 from Firefox plugin).
This is a pity, because it used to work just great!
  • dstillman
    First, you're not actually using the latest version of Zotero Standalone. You're on 4.0.8, which is months old.

    But your problem is likely unrelated to the Zotero version anyway.
    [JavaScript Error: "NS_ERROR_STORAGE_CONSTRAINT: Component returned failure code: 0x80630003 (NS_ERROR_STORAGE_CONSTRAINT) [mozIStorageStatement.execute]" {file: "chrome://zotero/content/xpcom/fulltext.js" line: 253}]
    Upgrade to the latest version and then check your database integrity in the Advanced -> Files and Folders pane of the Zotero preferences.
  • sci6676
    Thank you for the ultra-quick reply!

    I am actually running the latest (4.0.12) version of Zotero in Firefox, but you are right that the standalone version was older. I have upgraded in the meantime to 4.0.11 which seems to be the newest one I am being offered.

    At any rate I ran the integrity check on the database and it seemed indeed corrupted. So I followed the instructions at https://www.zotero.org/utils/dbfix/manual to repair the SQL database and then restarted the standalone Zotero. When I checked for database integrity it still showed it to be corrupted but this time it offered the option to try and repair it. After I did that another database integrity check was positive.

    So my problem seems to be solved now, but wouldn't it be better to offer the repair option right away when the NS_ERROR_STORAGE_CONSTRAINT error occurs?
  • dstillman
    OK, great.
    So my problem seems to be solved now, but wouldn't it be better to offer the repair option right away when the NS_ERROR_STORAGE_CONSTRAINT error occurs?
    Yeah, we'll do that. (We currently just check for NS_ERROR_FILE_CORRUPTED, which occurs when the file is pretty well damaged, but we can point people to the integrity checker when NS_ERROR_STORAGE_CONSTRAINT occurs.)
Sign In or Register to comment.