morfees

Results 18 comments of morfees

It was just a hypothesis, so I’m not entirely sure. As for reproducing the issue on Chrome for desktop, I haven’t been able to, my computer has significantly more RAM....

@pubkey I was able to reproduce it on a chromium browser on ubuntu : ![Image](https://github.com/user-attachments/assets/3e1ef197-a53f-4416-be48-ab8b8c626e40) I also have this error sometimes : ![Image](https://github.com/user-attachments/assets/729c6c98-6ca4-4ca9-9e2a-3af3ca4595a0) Since swapping indexDB with OPFS (+sharding), the...

I also feel like the app is using a lot more RAM with OPFS than with indexDB

> [@pubkey](https://github.com/pubkey) I was able to reproduce it on a chromium browser on ubuntu : > > ![Image](https://github.com/user-attachments/assets/3e1ef197-a53f-4416-be48-ab8b8c626e40) > > I also have this error sometimes : > > ![Image](https://github.com/user-attachments/assets/729c6c98-6ca4-4ca9-9e2a-3af3ca4595a0)...

> I also feel like the app is using a lot more RAM with OPFS than with indexDB with the OPFS storage, the is a memory leak somewhere, with IndexDB...

> does a restart fix the memory and it goes back to normal? Or will it start up again with the same amount of memory usage? For context the screenshot...

> Can you reproduce the memory leak without dev-mode? If it really is a memory-leak in the OPFS storage, let's find it together and I will fix that. This is...

The length will not exceed 20, we will change that. > Your schema does not have any indexes. This further indicates that there indeed is a memory-leak in OPFS storage...