Hmm, the other linked user has the same stopping point, and also mentioned a Chrome crash. I wonder if a recent Chrome update has made IndexedDB more sensitive to crashes. Can you try two separate things:

1. Reloading the page again now. I’ve just added a feature - you should see an ‘export’ button come up after several seconds when there’s an error like this, and that button allows you to do a data export which bypasses some of the “layers” to just grab the raw data. It’s possible that may hang/fail too, since I don’t yet know how “deep” we’ll need to go here. But also make sure you wait several minutes, and watch the console (like you screenshotted above), because if you’ve got a lot of data, the export could take a few minutes. If you see any errors in the console after you click the export button, please screenshot them.
2. Can you please try temporarily turning off all your browser extensions? I notice some extra logs there which aren’t caused by Perchance, and they could be a confounding factor that it’d be useful to eliminate as a cause.

Thanks @[email protected] for helping get the initial debug info!