[1.1.1.2] Dedicated Server (Linux) Memory Leak?

I wasn’t sure this was actually a bug at first, but my hypervisor (unraid) threw two OOM errors, one on the 26th last month, and another on the second, crashing my entire metal stack.

I since limited the docker container holding my dedicated condo (under a debian image, so by the books as far as distro goes) to 8G of memory, and I’ve noticed since restarting it around the 6th, through today, it went slowly up from 3G to 4G, then 5G, then a bit over 6.5G earlier today before I’d left for work, and when I got home, the docker container was not running again. The docker logs don’t indicate much; this seems to be the only relevant part, right before this is two users having connected and then disconnected after a bit, but it was also about 10 minutes before this line.

/opt/scripts/start-server.sh: line 112: 127 Killed ${SERVER_DIR}/Tower/Binaries/Linux/TowerServer-Linux-Shipping ${GAME_MAP} -log -nosteamclient -Port=${GAME_POR
T} -QueryPort=${QUERY_PORT} ${GAME_PARAMS}
[2025.11.08-18.31.12:185][409]LogNet: Verbose: UNetConnection::SetClientLogin

I have no idea why it would be killing the process like this other than running out of memory - again, this is the docker container log itself, so its not just the dedicated server log.

Given the behavior, I’m thinking there’s some kind of memory leak in the dedicated condo server, or at least the linux one.

Steps to Reproduce

I set up a docker container, using ich777/debian-baseimage:bullseye_amd64 as a base, which already contains steamcmd, and then installing the dedicated server per the linux dedicated condo instructions, and running it.

What I expected to happen

The server should just run, without slowly consuming more memory the time

What happened

I think I used to not see this because I had a cron job rebooting the server automatically once a day - I had to suspend it because of this bug, where rules weren’t saving, meaning the automatic reboot was inadvertently solving this bug, but given that was re-enabling/failing to save, I had to disable that, making this show up!

1 Like