destroy() race condition causing IndexedDB to hang

Still haven’t tracked this down, but opening up an issue so it doesn’t fall through the cracks.

I’ve managed to get IndexedDB in a state where it just doesn’t respond in Chrome after a few tests. Seems to be related to stale: update_after in map/reduce causing some parallelism. Weirdly, the tests complete when the Dev Tools are open, so we may have another Heiseinbug on our hands.

https://github.com/pouchdb/pouchdb/pull/3414 does not fix this particular bug.

[riterrani]

I am still having the same problem with this code

db.destroy().then(function (){ db = new PouchDB('test'); db.put(...); });

[pptdr]

It is reproducible in chrome browser each time when local db is cleared manually and recreate data during sync.

DOMException: Failed to execute ‘transaction’ on ‘IDBDatabase’: The database connection is closing. at openTransactionSafely (…) at allDocsQuery (…) at allDocs (…) at idbAllDocs (…) at PouchDB.idb_allDocs [as _allDocs] (…) at PouchDB.<anonymous> (…) at PouchDB.<anonymous> (…) at PouchDB.<anonymous> (…) at … at new Promise (<anonymous>)