Thanks for the extra details, and thanks for bearing with me here while we debug this.

I’ve just updated the chat page so you can now export the database with the button that pops up after several seconds when the page fails to load. And then once you’ve done that (remember it may take 5 minutes):

• It’ll save the export file to your device’s download folder
• You’ll notice that a ‘delete all data’ button appears below the export button, but don’t click that yet.
• Instead, to test that the exported file can be imported successfully, try opening an incognito/private/guest mode browser window, and visit https://perchance.org/ai-character-chat and import that file from your downloads folder using the ‘import’ button in the left side bar.
• If it works, then ideally backup the file from your downloads folder to google drive or dropbox or something, just to ensure 100% that you don’t lose it, because the next step is to go back to the page where you exported it and click that ‘delete all data’ button that appeared underneath the export button.
• Now reload the page, and import the file from your downloads folder using the import button, just like you did in the private browsing window.

The way the export process works is by skipping the ‘corrupt’ character that’s causing the underlying issue - it actually just replaces it with one of your other characters, and then changes its name to ‘CORRUPT’. So you’ll probably lose at least one of your characters, but you’ll still likely have all their chats, so you just need to re-write their name/description/etc.

Hopefully that works, but if not, then please let me know at which point it failed, and any error messages you saw.

Pinging @[email protected] since you mentioned you were experiencing the same issue after a ChromeOS crash. Also pinging @[email protected] and @[email protected] just in case you know of anyone on Discord/Reddit that had a similar issue. I’m fairly sure this is an IndexedDB issue (possibly specific to ChromeOS), by the way, so I’m not sure if it’s possible to fix the underlying cause, except by waiting for the ChromeOS/Chromium team to fix it.