Closed nikolaizombie1 closed 1 month ago
Thank you! Indeed, 0.1s sleep (or even longer) is probably not enough to load large wallpapers so it's better to do unload unused before preloading new. In this case, one unused wallpaper (that one that was just changed) will always stay in the memory (which is not a big deal), but I guess it's most sure way to change them quickly and reliably, so let's keep it this way. Also, then sleep before unload is not necessary I guess...
Thank you! Indeed, 0.1s sleep (or even longer) is probably not enough to load large wallpapers so it's better to do unload unused before preloading new. In this case, one unused wallpaper (that one that was just changed) will always stay in the memory (which is not a big deal), but I guess it's most sure way to change them quickly and reliably, so let's keep it this way. Also, then sleep before unload is not necessary I guess...
I'll remove the sleeps and see if it still functions reliably.
I removed the delays and it still worked reliably.
I fixed a bug where
hyprpaper
would unload wallpapers after being applied. In the majority of cases, the wallpaper would apply correctly in spite of them being unloaded from memory. However, larger wallpapers would be unloaded before being applied to the screen. The unload command worked as intended after the fix, it would drastically reduce the memory consumption ofhyprpaper
when viewing wallpapers inwaypaper
and effectively cap memory consumption instead of constantly growing as was happening before.