sqlite.jsm/better-bibtex.sql shutdown blocker problem: Zotero closing takes lots of time + export

MrMvMan

As I close the zotero, it close apparently but usually I have to wait few minutes (or kill it) to close with the below provided below.

This (probably) cause another error which when i restart all auto-export profiles with better-bibtex are gone and I have to restart setting up again. Even bbt generate the whole library citekeys again.

I check the integrity of sql database in zotero and it was OK.

zotero: 5.0.89 / linux
plugins: better-bibtex, zotfile

[CODE]
WARNING: At least one completion condition is taking too long to complete. Conditions: [{"name":"Sqlite.jsm shutdown blocker","state":{"description":"Waiting for connections to close","state":[{"name":"better-bibtex.sqlite#0: waiting for shutdown","state":{"identifier":"better-bibtex.sqlite#0","isCloseRequested":false,"hasDbConn":true,"hasInProgressTransaction":false,"pendingStatements":0,"statementCounter":7},"filename":"resource://gre/modules/Sqlite.jsm","lineNumber":250,"stack":["resource://gre/modules/Sqlite.jsm:ConnectionData:250","resource://gre/modules/Sqlite.jsm:OpenedConnection:1143","resource://gre/modules/Sqlite.jsm:openConnection/</<:953"]}]},"filename":"resource://gre/modules/Sqlite.jsm","lineNumber":148,"stack":["resource://gre/modules/Sqlite.jsm:null:148","resource://gre/modules/XPCOMUtils.jsm:get:194","resource://gre/modules/Sqlite.jsm:ConnectionData:250","resource://gre/modules/Sqlite.jsm:OpenedConnection:1143","resource://gre/modules/Sqlite.jsm:openConnection/</<:953"]}] Barrier: profile-before-change
WARNING: At least one completion condition is taking too long to complete. Conditions: [{"name":"better-bibtex.sqlite#0: waiting for shutdown","state":{"identifier":"better-bibtex.sqlite#0","isCloseRequested":false,"hasDbConn":true,"hasInProgressTransaction":false,"pendingStatements":0,"statementCounter":7},"filename":"resource://gre/modules/Sqlite.jsm","lineNumber":250,"stack":["resource://gre/modules/Sqlite.jsm:ConnectionData:250","resource://gre/modules/Sqlite.jsm:OpenedConnection:1143","resource://gre/modules/Sqlite.jsm:openConnection/</<:953"]}] Barrier: Sqlite.jsm: wait until all connections are closed
FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions: [{"name":"Sqlite.jsm shutdown blocker","state":{"description":"Waiting for connections to close","state":[{"name":"better-bibtex.sqlite#0: waiting for shutdown","state":{"identifier":"better-bibtex.sqlite#0","isCloseRequested":false,"hasDbConn":true,"hasInProgressTransaction":false,"pendingStatements":0,"statementCounter":7},"filename":"resource://gre/modules/Sqlite.jsm","lineNumber":250,"stack":["resource://gre/modules/Sqlite.jsm:ConnectionData:250","resource://gre/modules/Sqlite.jsm:OpenedConnection:1143","resource://gre/modules/Sqlite.jsm:openConnection/</<:953"]}]},"filename":"resource://gre/modules/Sqlite.jsm","lineNumber":148,"stack":["resource://gre/modules/Sqlite.jsm:null:148","resource://gre/modules/XPCOMUtils.jsm:get:194","resource://gre/modules/Sqlite.jsm:ConnectionData:250","resource://gre/modules/Sqlite.jsm:OpenedConnection:1143","resource://gre/modules/Sqlite.jsm:openConnection/</<:953"]}] At least one completion condition failed to complete within a reasonable amount of time. Causing a crash to ensure that we do not leave the user with an unresponsive process draining resources.
WARNING: No crash reporter available
[14944, Main Thread] ###!!! ABORT: file resource://gre/modules/Sqlite.jsm, line 148
[14944, Main Thread] ###!!! ABORT: file resource://gre/modules/Sqlite.jsm, line 148
[1] 14944 segmentation fault (core dumped) zotero -ZoteroDebug
[/CODE]

adamsmith

This sounds like it's squarely a better bibtex issue. Please report it on the project's github: https://github.com/retorquere/zotero-better-bibtex/issues/

emilianoeheyns

Yeah definitely BBT, something appears to be going wrong when BBT tries to close the DB connection.

MrMvMan

@emilianoeheyns , I still have this problem time to time. Do you find a solution?

emilianoeheyns

I don't yet know what the problem is, and I can't replicate it. But can you open an issue for this on github? You'll be asked by the label-gun bot to post a debug log, you can ignore that.

emilianoeheyns

I can replicate the problem -- the BBT db is corrupt. I'm working on a fix that'll allow it to start from a backup.