Closed Robby3St closed 6 months ago
Interesting.
I always assumed that reloading a page would free all resources of the previous instantiation.
I am currently running decker -S
on test/decks/media-deck.md
with a touch (and subsequent reload) in a 5 second loop and see an increase in memory from 500 MB to in 2,5 GB in just 2 Minutes on Safari.
Memory usage easily goes up to 10 GB which starts to increase memory pressure on the system.
A manual page reloads resets the memory usage of the tab immediately.
Only on Safari ...
Chrome behaves just fine.
In addition:
.decker/.shake.database
is getting quite large and larger on every reload (200 MB in one case where a user had ~ 15.000 files of external libraries he had to duplicate a lot (H5P embedded elements) - it seems like shake is corrupting its own database by writing bytes in ascending values to the .database - the write to the database also triggers a reload)
This is bad, but certainly not related, please open a new issue.
Also, i do not understand what you are saying here:
it seems like shake is corrupting its own database by writing bytes in ascending values to the .database
Closed in favour of #104.
The decker browser tab uses massive amount of RAM after running decker for an hour while slide development.