Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

OPFS errors in firefox-dev on Arch with sqlite.org wasm

more options

I'm developing a PWA website that relies heavily on the sqlite.org wasm libraries and origin private file system (OPFS). On firefox-dev 116.0b8 my website at app.kumaflash.com stopped being able to read the database it had been successfully using for months prior to that. I've also asked on the sqlite.org forum here: https://sqlite.org/forum/forumpost/3bb8b83c45 but haven't found any solutions yet.

You can see a thrown together video of the app working normally here: youtube.com/@kumaflash

and the error I receive is: OPFS syncer: xRead() async error: GetSyncHandleError: Error getting sync handle for xRead(). 6 attempts failed. kumaflash.db : NotFoundError: Entry not found

If I manually open the OPFS in the console I can see that the file is there with this helper function in my app: var p = await _app.xdcards._lsOriginPrivateFSDir("/"); //that's an L for list ListOriginPri...

Additionally I can't debug because the firefox debugger crashes whenever I try to inspect my app. The debugger crashes on firefox-dev and release versions on every computer I've tried (with this app only). The chromium debugger works but the error doesn't happen there.

Any ideas on what I should try?

I'm developing a PWA website that relies heavily on the sqlite.org wasm libraries and origin private file system (OPFS). On firefox-dev 116.0b8 my website at app.kumaflash.com stopped being able to read the database it had been successfully using for months prior to that. I've also asked on the sqlite.org forum here: https://sqlite.org/forum/forumpost/3bb8b83c45 but haven't found any solutions yet. You can see a thrown together video of the app working normally here: youtube.com/@kumaflash and the error I receive is: OPFS syncer: xRead() async error: GetSyncHandleError: Error getting sync handle for xRead(). 6 attempts failed. kumaflash.db : NotFoundError: Entry not found If I manually open the OPFS in the console I can see that the file is there with this helper function in my app: var p = await _app.xdcards._lsOriginPrivateFSDir("/"); //that's an L for list ListOriginPri... Additionally I can't debug because the firefox debugger crashes whenever I try to inspect my app. The debugger crashes on firefox-dev and release versions on every computer I've tried (with this app only). The chromium debugger works but the error doesn't happen there. Any ideas on what I should try?
Captures d’écran jointes

Toutes les réponses (5)

more options

I don't see this error but I don't have an existing database.

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

more options

It looks like the SQLite library works with the browser's IndexedDB interface (judging from where things appear in the Storage Inspector, Shift+F9). Does the library have any kind of verbose messaging so that it could provide more information about problems working with that interface? That might help by returning more searchable terminology.

more options

@zeroknight, thanks I'll try that and post my results.

more options

@jscher2000, thanks I'm using sqlite.org's library instead of the original sqlite.js library which has been around longer. I'm using OPFS with the sqlite.org version.

Sorry, I should have mentioned that there is a place in indexeddb for media files and also sqlite databases but the databases are only stored there when I'm not using sqlite.org. The app can work with either library because I'm testing which version works better. I'm troubleshooting the OPFS version specifically at the moment though.

Modifié le par donb4

more options

(Hi donb4, your last reply is temporarily hidden because it contained a link to a non-Mozilla site. It should become visible later today.)