Firefox freeze on trying to open an item saved in Zotero

PinaColada
A site I have saved to Z appears as
zotero://attachment/631/ when klicking on it
Firefox would then freeze. I have to force quit Firefox.

This does not happen to the other saved items
  • adamsmith
    is that a publicly accessible page? Do you have a URL?
  • PinaColada
    http://www.svd.se/mat-och-vin/matkultur/annat-an-sagans-snalla-jattar_8790042.svd
  • adamsmith
    you don't get an unresponsive script warning? That's what's happening for me and is due to a javascript running on that page.

    On the other hand -
    @Dan - when I imported this into my regular Zotero running on branch, Zotero threw a corrupted database error and I had to restart and restore from the last back-up. I can't replicate that on my dev profile running from the git source (and I'm not all that keen on crashing my work profile repeatedly), so it might have been a fluke or another add-on, but I thought I'd flag it. Tried to upload the damaged db to the repair tool, but server timed out on me (file size is 55MB).
  • dstillman
    Does the db show as corrupted from the prefs?
  • adamsmith
    I never got that far - it threw the error - multiple times, I had to force quite Firefox and next time it started it automatically went to the automatic backup.
    But if need be I can try using this db in a fresh profile
  • dstillman
    If the old DB passes the integrity check without errors, it'd be good to see if the new one was actually corrupted. You can also do that from the command line by running 'sqlite3 zotero.sqlite.damaged' (or with the path to the file if you're not in that directory) and then 'PRAGMA integrity_check;' at the SQLite prompt.
  • adamsmith
    both old and new database show up as corrupted.
    Are you interested in any debug before I try to repair this?
  • dstillman
    No, that's OK. We've been seeing a lot of this lately, likely due to increased database sizes from full-text syncing.
  • adamsmith
    ok, fixed by the built-in repair function.
  • dstillman
    adamsmith: Do you happen to still have a copy of the supposedly damaged database? If so, could you try the SQLite command above on it? I'm confused as to why we're getting so much of these corruption messages, and I'm wondering if they're actually spurious errors. Generally speaking, the integrity check shouldn't be able to fix database corruption — only data inconsistency, but that shouldn't trigger the corruption error.
  • adamsmith
    I actually have a whole bunch of them, but I'm not sure which is which.

    I'm pretty sure I tracked down what caused this in my case, namely that ZFF didn't close down properly when I opened ZSA - I had both the Zotero pane and ZSA pointing to the same database open at the same time. I was about to report that, but as these things are, the moment I wanted to systematically reproduce this and send debug, it stopped happening and I haven't been able to reproduce it since.

    In any case, the output for the integrity check for what I believe was the first case and then one other case is here:
    https://gist.github.com/adam3smith/7913463
  • dstillman
    If you're able to tell, I'd be curious to know the date of the earliest corrupted database (and the last uncorrupted one).
  • adamsmith
    the first time I got the "corrupted" message was when I posted above, 6 days ago.
    My current database passes the integrity check - that's been the case for all but the first time I had to restart because of corruption.
Sign In or Register to comment.