Dan Christensen

I had some crash problems after moving the public-test build forward and basically resolved it by: * remove all the "BepInExPack Valheim" files/directories * validate the install in Steam to...

I had mixed results with trying to use the "BepInExPack Valheim" releases too, which is why I went to the standard BepInEx release. > from what I understand thus shoving...

@zekkoh I tried using the Thunderstore Mod Manager 1.33.0 and a clean Valheim directory and was able to get it to launch successfully by clicking the "▶Modded" button. I tried...

Do you know where the world save is landing? If it's in some tmpfs this might make sense. Otherwise, with such a reproducible problem, it should be pretty simple to...

Then you should monitor for growth in /proc/meminfo and see which entry grows. And also review the meminfo section of [proc.txt](https://www.kernel.org/doc/Documentation/filesystems/proc.txt) for more detail. But the conventional wisdom is that...

@fuse1985 if you look in the running Docker container, and your backups are going to /backups, what does `df -h /backups` show? (or wherever your backups are going)

I was thinking it could be a tmpfs, but doesn't seem to be... Seems like you must also be setting `BACKUPS_DIRECTORY` if it's not `/config/backups` though?

If that's the case you should be able to recover the memory using `/proc/sys/vm/drop_caches`: ``` /proc/sys/vm/drop_caches (since Linux 2.6.16) Writing to this file causes the kernel to drop clean caches,...

If dropping the caches recovers the memory thought to be going to a leak it's safe to do nothing going forward.

@jonvel Please also collect some additional data: `docker stats --no-stream --no-trunc ` I imagine this is an artifact of an older portainer, prior to v1.20.0 which introduced separating out the...