Hi, i have an issue with my MInecraft Servers
The RAM Just Yeets into the sky when multiple people travel whatever i do
Fabric, Forge, Vanilla, With mods and without
The Server RAM is just rocketing into the sky and the server crashes in like 2-3 Min
Then it crashes with the Pterodactyl Error 137 Out of Memory
Its not playable like this but idk what to do
#Minecraft Servers full memory
42 messages · Page 1 of 1 (latest)
What's your start-up command currently set to?
How much memory did you assign to the server ?
i tried with 8, 12 16 and 18
all the same
it just takes longer
thats from a video i made
3sec later
so for this time it took 1min 25sek to crash the server
that happens aswell in this world
in others
even other docker images i made
could you tell me where i find that?
It's there on your startup tab
Try pushing your MaxRAMPercentage down to 80 and make sure there isn't a MaxRAMPercentage or Xmx set in the unix_args.txt file
yesterday we did that with 5 players
right now we are 2 players and cant replicate it with that changed
it could be fixed but i dont really know
its on 5gb ram right now
ill try it with our big map when its uploaded
and idk hot to get to the unix file
oh sorry for ping
does someone else know what to do maybe?
Get more memory. Multiple people in ur server, all traveling, loading chunks etc, can be quite memory intensive
i had it to 16 gb of ram
no its not the ram issue
i mean it fills in minutes to over 10gig
You got mods or plugins?
When i see this, it's almost always related to a mod, sometimes a plugin, and very rarely I've seen it caused by someone taking the cache folders with them from another host and fixed it by deleting all non-vital data folders such as worlds or plugin/mod folders
you don't have an xmx set? I've never seen the maxrampercentage argument personally, but you can try replacing that with an xmx (just a thought)
the problem is the mod "spark" tells me something different
when the panel shows 7gb spark says 2,1gb
yeah i tested that already but dint worked in this case
Pterodactyl now sets it to like 80 automatically with the new Java version iirc. Not sure exactly
is there really no one who knows something? qwq
I had this problem. I think, don't quote me on this, it's because docker runs kinda like a vm. The memory you allocate to the ptero server != the amount of memory you can use, some of it is taken up by linux in docker. Then, if you take too much memory, the linux in docker kills it for OOM. I don't know if that last part is true.
I fixed mine by messing with the ram until it was just right - not too low, not too high.
I actually read from the guy known for making advanced gc jvm arguments, apparently allocating 100% of the available memory means that minecraft can't actually use all the memory, because the jvm needs some overhead itself. I don't believe the subsystem has any or much effect because it isn't a full vm. So that's why pterodactyl by default uses a max of 80% memory in the jvm args. If you tell mc to use all the memory, it can't and freezes while trying
Ah, that makes sense