starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 22:25:59 +03:00

[GH-ISSUE #1781] Killing Floor 2 100% CPU usage #1394

New issue

Closed

opened 2026-02-27 02:56:51 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:56:51 +03:00

Owner

Originally created by @Lartza on GitHub (Jan 19, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1781

Running the Killing Floor 2 server with LGSM on Arch causes one of the server processes to lock a CPU core at 100% and making the game unplayable due to desync and lag. The process locks this usage even without any players though.

Downloading the server manually from steamcmd and just running it works perfectly.

postdetails:
https://gist.github.com/Lartza/e19c9181e020cba8a54ddd83e8a740e2

I have a suspicion it's something to do with some library fixes lgsm applies that on Arch would be better to not have and use system libraries for everything, but I am unsure on how to try that.

The console log does not indicate any issue and is identical to the server running without lgsm.

Originally created by @Lartza on GitHub (Jan 19, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1781 Running the Killing Floor 2 server with LGSM on Arch causes one of the server processes to lock a CPU core at 100% and making the game unplayable due to desync and lag. The process locks this usage even without any players though. Downloading the server manually from steamcmd and just running it works perfectly. postdetails: https://gist.github.com/Lartza/e19c9181e020cba8a54ddd83e8a740e2 I have a suspicion it's something to do with some library fixes lgsm applies that on Arch would be better to not have and use system libraries for everything, but I am unsure on how to try that. The console log does not indicate any issue and is identical to the server running without lgsm.

kerem closed this issue

2026-02-27 02:56:51 +03:00

kerem commented

2026-02-27 02:56:52 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 19, 2018):

What about a debug mode start?
That will help us know if it's TMUX related or not.
https://github.com/GameServerManagers/LinuxGSM/wiki/Debug

Also, what are your start parms when running the server manually?
Maybe try with these parms inside LGSM.

That will help understanding more about this.

@UltimateByte commented on GitHub (Jan 19, 2018): What about a debug mode start? That will help us know if it's TMUX related or not. https://github.com/GameServerManagers/LinuxGSM/wiki/Debug Also, what are your start parms when running the server manually? Maybe try with these parms inside LGSM. That will help understanding more about this.

kerem commented

2026-02-27 02:56:52 +03:00

Author

Owner

@Lartza commented on GitHub (Jan 19, 2018):

I messed up my startup parameters and that made me accidentally figure out the issue.

The config files at
https://github.com/GameServerManagers/Game-Server-Configs/tree/master/KillingFloor2
cause this, letting the server generate it's own the issue disappears.

@Lartza commented on GitHub (Jan 19, 2018): I messed up my startup parameters and that made me accidentally figure out the issue. The config files at https://github.com/GameServerManagers/Game-Server-Configs/tree/master/KillingFloor2 cause this, letting the server generate it's own the issue disappears.

kerem commented

2026-02-27 02:56:52 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 19, 2018):

You can submit a PR on the config repo with proper configs if you wish. :)

@UltimateByte commented on GitHub (Jan 19, 2018): You can submit a PR on the config repo with proper configs if you wish. :)

kerem commented

2026-02-27 02:56:52 +03:00

Author

Owner

@Lartza commented on GitHub (Jan 19, 2018):

I'll do that after sleep :) Thanks for your help

@Lartza commented on GitHub (Jan 19, 2018): I'll do that after sleep :) Thanks for your help

kerem commented

2026-02-27 02:56:52 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jan 19, 2019):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jan 19, 2019): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.