Deleting IndexedDB can result in inability to connect to the database until you restart Chrome

[rtibbles]

Summary

Wiping out the IndexedDB can lead to this error happening whenever it is then accessed, even after a page refresh:
Uncaught (in promise) Error: InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.

This seems to be an issue in Chrome specifically, and is widely reported on many libraries using IndexedDB:
tutao/tutanota#452
localForage/localForage#581
localForage/localForage#694
firebase/firebase-js-sdk#1926
pouchdb/pouchdb#3415
jensarps/IDBWrapper#80

And twice in Dexie.js:
dexie/Dexie.js#613
dexie/Dexie.js#934

Category

BUG

Usage Details

This seems to be somewhat difficult to reproduce, but once it does, the only way to get rid of it is to restart Chrome.

[kollivier]

It has reproduced quite reliably for me, and seems to not take long after I start using Studio for it to occur. I think the first time I remember seeing it was while trying to switch users, though I don't know if that's directly related in any way.

[kollivier]

Another possibility is that I've found I often need to clear out indexedDB due to seeing incorrect data (e.g. channel list, etc.) displayed in the browser, for reasons I haven't yet completely nailed down. (I know issues with switching users is part of the cause, but does not explain all the issues.)

[nucleogenesis]

I am tickled that I found this issue by Googling the Chrome error message, finding jensarps/IDBWrapper#80 and scrolling down to see @rtibbles and a link to here.

the only way to get rid of it is to restart Chrome

Can confirm ^ thanks!