Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gui] OPFS VFS handlers can get stuck in an unusable state in specific edge cases #777

Open
dskvr opened this issue Feb 27, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@dskvr
Copy link
Collaborator

dskvr commented Feb 27, 2025

This is an oversight within the OPFS, VFS and SAHPOOL api in browsers, and I cannot control it. I need to wipe OPFS store when this happens. The difficulty is that the detection of this state is impossible, so it needs to be greedy and just wipe and the reinstantiate when the number of connection failures reaches a certain threshold.

  • Wipe OPFS in the namespace
  • Wipe synchronization timestamps

This will result in the bootstrap running again, which is bad UX, but still infinitely better than cache never working again. The unusable state is irrecoverable event after browser restarts.

@dskvr dskvr added the bug Something isn't working label Feb 27, 2025
@dskvr
Copy link
Collaborator Author

dskvr commented Mar 1, 2025

Actually not a case of unusable state, it's db corruption which can be caught by parsing the error and using some methods provided by sqlite to wipe the store

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant