Ark Multiple Processes Aren't Killed
Posted: Mon May 08, 2017 11:49 pm
When Ark is configured to update mods on startup (by adding modids to game.ini), before it starts the server (the process is active but server hasn't started yet) it starts steamcmd which starts a console window.
Problem is that if the server is stopped or restarted before steamcmd has a chance to complete. The processes stay active and if the server is started again and stopped again then a second instance of these processes are not closed again. The main problem with this is the steamcmd process uses all available cpu.
Note: I have "Kill child processes" checked on the options page and it isn't fixing this issue.
Problem is that if the server is stopped or restarted before steamcmd has a chance to complete. The processes stay active and if the server is started again and stopped again then a second instance of these processes are not closed again. The main problem with this is the steamcmd process uses all available cpu.
Note: I have "Kill child processes" checked on the options page and it isn't fixing this issue.