Chrome Browser Error

Update for March 29, 2022

Chrome version 100.x has been released. You may need to force an update to your browser if you are still using version 99.x after rebooting your browser/device.

Original Report

We received reports of errors for users of Cascadin after upgrading to the latest version of the Chrome browser (version 99.0.4844). Impacted users may not be able to log in or remain logged into Cascadin. Here’s what you can do to resolve this Chrome browser error.

We strongly recommend using another supported browser such as Firefox or Safari until this has been resolved. Other Chromium based browsers such as Microsoft Edge and Brave may be impacted by this bug.¹

This is actively being investigated by the Chromium team. The bug should be mitigated with the versions of Chromium that are currently in Beta release channels for both Chrome and Edge with expected releases at the end of March.²

Their team has made the follow recommendations for workarounds to the bug.

Other Workarounds

Workaround 1: Create a new profile.

This approach allows you to work around the underlying issue without affecting your current profile.

1. On your computer, open Chrome.
2. At the top right, click Profile Profile.
3. Click Add.
4. If you choose to Sync to your Google Account, your profile name will automatically be your Account name.
5. Choose a name, photo and color scheme.

These instructions were taken from https://support.google.com/chrome/answer/2364824?#7110673

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 “What changes when you restore your settings” in the below support link for more information.

1. On your computer, open Chrome.
2. At the top right, click More More and then Settings and then Advanced.
3. 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.

These instructions were taken from https://support.google.com/chrome/answer/3296214

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, we recommend copying these instructions to a text file as you will have to close Chrome.

1. Open chrome://version in Chrome and look for the “Profile path” value. It should look something like one of the following OS-specific values:
   • Windows: “C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default”
   • macOS: “Users/MyUserName/Library/Application Support/Google/Chrome/Default”
   • Linux: “/home/MyUserName/.config/google-chrome/Default”
2. Navigate to this path in your operating system’s file browser.
3. Completely exit Chrome.
4. Delete the “QuotaManager” and “QuotaManager-journal” entries inside this directory. Using the Windows example path above, the files would be:
   • C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default\QuotaManager
   • C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default\QuotaManager-journal
5. Reopen Chrome.

Updates

1. The bug may impact Chromium-based browsers that are using Chromium M99.
2. Mitigation and fixes for the bug are included in Chromium M100 and M101. Chromium M100 is currently in beta release for both Chrome and Edge and it is scheduled for stable release at the end of March.