`Failed to read large IndexedDB value` error - Githubissues

pixiebrix / pixiebrix-extension

PixieBrix browser extension

https://www.pixiebrix.com

GNU Affero General Public License v3.0

83 stars 22 forks source link

`Failed to read large IndexedDB value` error #9211

Open twschiller opened 2 days ago

twschiller commented 2 days ago

Describe the bug

Discussion

I'm not sure user-facing impact. But this error showed up frequently for a user who has seen the IndexedDB unresponsive banner: https://mixpanel.com/project/2202701/view/143273/app/insights/#report/63816248
For triaging, one improvement we might want to make for IndexedDB errors is report which DB/table encountered the problem. E.g., the log DB being corrupted is less of a problem than the local package registry

Resources

Chrome Roadmap: Feature: Improved error reporting in IndexedDB for large value read failures
Chrome Bug Tracker: https://issues.chromium.org/issues/342779913

Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Extension Version: CWS version, at least 2.1.1 and 2.1.2

grahamlangford commented 2 days ago

For triaging, one improvement we might want to make for IndexedDB errors is report which DB/table encountered the problem. E.g., the log DB being corrupted is less of a problem than the local package registry

Great callout, I will definitely implement that

grahamlangford commented 2 days ago

This error is being reported by reportError which is not supposed to happen anymore. I'll have to trace the callstack and find out why