- Notifications
You must be signed in to change notification settings - Fork83
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
Hello, I am using wa-sqlite instead of the official SQLite wasm because I like the wa-sqlite interface better. But I'm running into an issue in Safari that looks like it is the same thing as: But I'm getting it as an unhandled exception. I'm not completely sure if it is the same thing. This is how I am initializing (in a Worker): I get the error as an unhandled rejection: Doing the above doesn't fix it, but just creates more |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 1 comment 1 reply
-
My guess would be that you have multiple contexts accessing the same OPFS files, e.g. you have multiple tabs open on your page or one page is opening multiple Workers. AccessHandlePoolVFS works only on one context at a time. Apart from that you haven't provided enough information for me to debug it (such as the wa-sqlite version, a stack trace, whether it works on other browsers, etc.) without investing a lot of effort. I suggest creating a test web page with aminimal reproducible example that shows the bad behavior, e.g. using GitHub Pages. Alternatively, you can look at how thedemo handles initialization indemo-worker.js, or the much simplerhello demo (you'll need to change its VFS), and see where what you're doing diverges. |
BetaWas this translation helpful?Give feedback.
All reactions
-
Thank you for the response. |
BetaWas this translation helpful?Give feedback.