Zotero-better-bibtex: (Large) bibtex file import hangs (OSX beachball, no interaction possible)

Created on 10 Nov 2020  ·  7Comments  ·  Source: retorquere/zotero-better-bibtex

Report ID: I2NRN9LD-euc (However, please note that because Zotero hangs, I cannot give a report just after the bug, of course. I figured it might still be useful for you to have the info from the report before the error.)

bibfile.bib.zip

I select "File -> Import..." and choose this file in the wizard. I expect it to import the bibtex database file into my library.

Zotero is pegged at 100% CPU utilization for hours and I get a "beachball" in OSX. I cannot interact with the log window after the hang, but here's a screenshot:

Screenshot 2020-11-10 at 13 40 31

(Sorry, I know it is horrible to post a screenshot of a text log, but I can't interact with the window).

bug

All 7 comments

I have this reproducible, and the approximate cause. On it.

thanks (I see "awaiting user feedback" but I'm not sure to what that refers - let me know if I can provide any more info)

That's just @label-gun -- more often than not, if I comment, it's because I need more info, and that happened often enough that I automated it, but that's not the case here, so I should have manually unlabeled it. I think I have a fix, but my testing service has been acting up today, and I've been waiting for over 3 hours for the build to clear. I've set up my release chain so that I can't release untested builds, so I'm afraid I'll have to wait for the last test to pass.

:robot: this is your friendly neighborhood build bot announcing test build 5.2.85.7372 ("Merge branch 'master' into gh-1692")

Install in Zotero by downloading test build 5.2.85.7372, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Successfully imported; thanks.

Cool, fix is in the new release. You'll be upgraded automatically, but it's just what you have now with a formal build number slapped on.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings