17 March 2022
In the recent update to Chrome 99 a number of users have encountered a bug where the in-browser database stops working. We received reports of this from GoFullPage users. Here are some steps to mitigate the issue.
The Chrome team has been helpful in tracking this issue and the following notes are mostly copied from Simeon’s response on this bug—thanks, Simeon et al.!
- InvalidStateError: An operation that depends on state cached in an interface object was made but the state had changed since it was read from disk.
- DOMException: Internal error retrieving bucket data directory
- UnknownError: Internal error opening backing store for indexedDB.open
See the workarounds below. If you’re up for it (especially if you know your way around a terminal), then I recommend doing option 3, but the quickest way to get something going in a time crunch is option 1.
Workaround 1: Create a new profile
The issue is profile-specific. So if you create a new one or switch to another you can likely get around this issue. It’s the quickest way to get around this issue.
See instructions to add or switch a profile on support.google.com.
- On your computer, open Chrome.
- At the top right, click the circular Profile image.
- Click Add or select another one.
- Try the extension here (install it first if necessary since extensions are installed per-profile)
Workaround 2: Reset your current profile
This allows you to continue using Chrome as you normally do, but many features will go back to default settings. See these instructions on resetting your profile for info on what gets reset and what remains.
- On your computer, open Chrome.
- At the top right, click the 3 dots for “More” and then Settings and then Advanced.
- Follow the appropriate instructions for your operating system
- On Chromebook, Linux, and Mac: Click Reset settings and then Restore settings to their original defaults and then Reset settings.
- On Windows: Click Reset and cleanup and then Reset settings to their original defaults and then Reset settings.
Workaround 3: Manually delete your QuotaManager database
This approach will surgically address the underlying database corruption without affecting your profile settings. The QuotaManager database will be rebuilt next time Chrome starts.
Before proceeding, copying these instructions to a text file as you will have to close Chrome.
- Enter the URL
chrome://versionin the URL bar of Chrome
- Search for the key "Profile Path" and copy the value, which should look something like the following (note: each profile has a unique path):
- Navigate to this path in your operating system's file browser (likely easier from the terminal if possible)
- Completely exit Chrome.
- Delete the "QuotaManager" and "QuotaManager-journal" entries inside this directory. Using the Mac example from above it would look like this:
rm "/Users/MyUserName/Library/Application Support/Google/Chrome/Default/QuotaManager" rm "/Users/MyUserName/Library/Application Support/Google/Chrome/Default/QuotaManager-journal"
6. Reopen Chrome.
If you’re encountering this issue and tried one of the workarounds, let me know below. If you want to contact support for the extension, then just follow the prompts in the extension and someone will help you out!