starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-24 21:56:01 +03:00

[GH-ISSUE #3056] Project Zomboid -Xms -Xmx Java/JVM memory options are not honored in start-server.sh & ProjectZomboid64.json #2162

New issue

Closed

opened 2026-02-27 03:01:15 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 03:01:15 +03:00

Owner

Originally created by @0xPerseus on GitHub (Sep 21, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3056

User Story

N/A

Basic info

Distro: [Ubuntu 20.04.1 LTS]
Game: [Project Zomboid]
Command: [,/pzserver start]
LinuxGSM version: [v20.5.0]

Further Information

The JVM memory options, (-Xms, -Xmx) specified within the serverfiles/start-server.sh & ProjectZomboid64.json are not passed onto the JVM. Pre-allocation of memory never exceeds 2048m. This can be observed by running top/htop and monitoring the memory usage of the process.

To Reproduce

Steps to reproduce the behavior:

Go to '/home/pzserver/serverfiles'
Modify '/home/pzserver/serverfiles/start-server.sh' & '/home/pzserver/serverfiles/ProjectZomboid64.json'
Modify the lines containing, -Xms2048m & -Xmx2048m - change the initial pre-allocation value to something higher (-Xms)
Start the game server './pzserver start'
Run 'htop' and observe the total allocated memory for the JVM instance

Expected behavior

The Java/JVM Xms and Xmx settings should both pre-allocate the amount of memory to start along with the maximum defined value to designate to the Java/JVM instance.

Originally created by @0xPerseus on GitHub (Sep 21, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3056 ## User Story N/A ## Basic info * **Distro:** [Ubuntu 20.04.1 LTS] * **Game:** [Project Zomboid] * **Command:** [,/pzserver start] * **LinuxGSM version:** [v20.5.0] ## Further Information The JVM memory options, (-Xms, -Xmx) specified within the serverfiles/start-server.sh & ProjectZomboid64.json are not passed onto the JVM. Pre-allocation of memory never exceeds 2048m. This can be observed by running top/htop and monitoring the memory usage of the process. ## To Reproduce Steps to reproduce the behavior: 1. Go to '/home/pzserver/serverfiles' 2. Modify '/home/pzserver/serverfiles/start-server.sh' & '/home/pzserver/serverfiles/ProjectZomboid64.json' 3. Modify the lines containing, -Xms2048m & -Xmx2048m - change the initial pre-allocation value to something higher (-Xms) 3. Start the game server './pzserver start' 4. Run 'htop' and observe the total allocated memory for the JVM instance ## Expected behavior The Java/JVM Xms and Xmx settings should both pre-allocate the amount of memory to start along with the maximum defined value to designate to the Java/JVM instance.

kerem

2026-02-27 03:01:15 +03:00

closed this issue
added the
game: Project Zomboid

waiting response
labels

kerem commented

2026-02-27 03:01:15 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Sep 21, 2020):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Sep 21, 2020): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.94. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 03:01:15 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 21, 2020):

I do not know what you expect it to do when you set higher values there, but usually the server only takes at first what it needs.
RAM allocations are done when needed and it does not allocate all at the start.

Anyway the arguments via the json file seem to work:

Tried this and got this in my log:

pzexe: vmArg (json) 1: -Xms4096m
pzexe: vmArg (json) 2: -Xmx4096m

These are all default values.
If you expect something else, maybe you need to ask on the PZ discord or forum.

@h3o66 commented on GitHub (Sep 21, 2020): I do not know what you expect it to do when you set higher values there, but usually the server only takes at first what it needs. RAM allocations are done when needed and it does not allocate all at the start. Anyway the arguments via the json file seem to work: Tried this and got this in my log: ``` pzexe: vmArg (json) 1: -Xms4096m pzexe: vmArg (json) 2: -Xmx4096m ``` These are all default values. If you expect something else, maybe you need to ask on the PZ discord or forum.

kerem commented

2026-02-27 03:01:15 +03:00

Author

Owner

@0xPerseus commented on GitHub (Sep 21, 2020):

I do see the vmArg's being passed over, that's not the issue, the issue is that, the Xms, which is the initial memory allocation pool, does not reflect what is being set. If it were, similar to how it's done with a Minecraft server for example, you'd see the process actually pre-allocating whatever has been specified. To the best of my knowledge, this is how it should operate otherwise, those values have no meaning / value. If this is a PZ issue and not one related to LGSM, I'll raise this to them directly.

@0xPerseus commented on GitHub (Sep 21, 2020): I do see the vmArg's being passed over, that's not the issue, the issue is that, the Xms, which is the initial memory allocation pool, does not reflect what is being set. If it were, similar to how it's done with a Minecraft server for example, you'd see the process actually pre-allocating whatever has been specified. To the best of my knowledge, this is how it should operate otherwise, those values have no meaning / value. If this is a PZ issue and not one related to LGSM, I'll raise this to them directly.

kerem commented

2026-02-27 03:01:16 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 21, 2020):

Also interesting is this:
https://pzwiki.net/wiki/Startup_parameters

You could set the arguments on the script/server with this

Startup parameters - PZwiki

Edit for basic usage of the own start paremter have a look here:
https://docs.linuxgsm.com/configuration/start-parameters

@h3o66 commented on GitHub (Sep 21, 2020): Also interesting is this: https://pzwiki.net/wiki/Startup_parameters You could set the arguments on the script/server with this <blockquote><img src="/favicon.ico" width="48" align="right"><div><strong><a href="https://pzwiki.net/wiki/Startup_parameters">Startup parameters - PZwiki</a></strong></div></blockquote> Edit for basic usage of the own start paremter have a look here: https://docs.linuxgsm.com/configuration/start-parameters

kerem commented

2026-02-27 03:01:16 +03:00

Author

Owner

@0xPerseus commented on GitHub (Sep 21, 2020):

Thanks for that @h3o66 I will make a few modifications on my end and see if passing those args has the intended effect and report back.

@0xPerseus commented on GitHub (Sep 21, 2020): Thanks for that @h3o66 I will make a few modifications on my end and see if passing those args has the intended effect and report back.

kerem commented

2026-02-27 03:01:16 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 24, 2020):

Did anything work here for you ?

@h3o66 commented on GitHub (Sep 24, 2020): Did anything work here for you ?

kerem commented

2026-02-27 03:01:16 +03:00

Author

Owner

@h3o66 commented on GitHub (Dec 23, 2020):

No answer in more than 2 months.
~closing

@h3o66 commented on GitHub (Dec 23, 2020): No answer in more than 2 months. ~closing

kerem commented

2026-02-27 03:01:16 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 24, 2021):

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

@github-actions[bot] commented on GitHub (Dec 24, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:54:47 +03:00

[PR #2162] [MERGED] feat(newserver): Atlas #3516