Recovering from "Internal error opening backing store for indexedDB.open" errors

363 views
Skip to first unread message

Todd Schiller

unread,
Oct 10, 2024, 6:37:04 PM10/10/24
to Chromium Extensions
We have an enterprise customer using our extension on Citrix. 2 of 40 users are encountering an "Internal error opening backing store for indexedDB.open" error on all IndexedDB calls.

Previously when seeing flakiness for other users, e.g., "Failed to read large IndexedDB value" errors (which can indicate a missing blob), we added code to automatically mitigate by deleting the DB so it could be recreated

Our current guess for these 2 users is that their Chrome profile is becoming corrupted.  Having the Citrix admin delete the IndexedDB directory on the filesystem temporarily fixes the problem. But the problems have returned, e.g., when coming in the next day or after a lunch break

Any ideas of how to automatically mitigate in our extension code? We suspect it's a Citrix profile syncing/streaming issue, so we're following up with the Citrix admin on their Profile Management settings

Thanks,
Todd

Resources:


Todd Schiller

unread,
Oct 17, 2024, 10:34:29 AM10/17/24
to Chromium Extensions, Todd Schiller
Following up here -- we're pretty confident the issue is related to streaming. Some main takeaways from our investigation:
  • The default Citrix profile synchronization policy includes a lot of Chrome profile information that can slow desktop load times
  • Naively turning on Profile Streaming to combat the slow load times can cause Chrome profile/data corruption issues, especially with IndexedDB
  • If you're using IndexedDB for persistence, ensure it's excluded from profile streaming. If you're just using IndexedDB as a cache, exclude IndexedDB from profile synchronization

Todd

Reply all
Reply to author
Forward
0 new messages