After running a 1.4.2 server for a while i have to restart the server cause the memory reached 100% on a 4 gig server with 8 people on it
Linked issues
is duplicated by 2
Comments 12
Possible duplicates: #1125 #2917; I'm commenting here because it was the oldest report I could find.
I'm running the minecraft server for two players max on FreeBSD 9.1 with 4GB RAM. I tried several JVM: diablo 1.6.0, sun jdk 1.6.0, openjdk7, all compiled from the ports system. The server is currently running with jdk1.6.0 using
JAVA_HOME=/usr/local/jdk1.6.0 java -Djava.security.egd=file:/dev/random -Xmx2048M -Xms512M -jar minecraft_server.jar nogui
Before Minecraft 1.4.2 I used weekly snapshots and every 3-4 days the server would crash with an out of memory exception. This bug was finally fixed with 1.4.2 and once I updated the server to 1.4.2 it ran without a single restart for 3 weeks. With 1.4.2 the server would consume ~150-200MB RAM while no one is logged in. Since yesterday I'm running 1.4.4 and the server is showing similar symptoms as it did with pre-1.4.2 versions: After a fresh start consuming at least 300MB RAM, when two people log in it jumps up and won't go below 500MB after they logged out. But I guess it's too soon to draw any conclusions.
Is this still a concern in the current Minecraft version? If so, please update the affected versions
in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I'm still testing and watching my server. Right now it looks like memory usage is increased in 1.4.4 compared to 1.4.2 but it doesn't look like there's something leaking. I'll keep an eye on my server and will update next weekend.
This issue still does not seem to be fixed. Minecraft's debug screen shows Minecraft using about 400 mb but in the windows task manager it shows it using up over 1 gb.
The task manager shows the amount of memory assigned to the JVM, which is always 1GB, see the command line paramter -Xmx1024m
But when I start the world task manager is well under 1 gb. And even when I allocate minecraft with only 500 mb task manager shows it going over that limit.
That's how the allocator of Java works: Freed memory is not really freed, only when the amount of maximum memory is reached, the gargabe collector kicks in.
I see when -Xmx512m is given, it will allocate > 1GB.
But nevertheless, that all is not a Minecraft isssue, that's some OS and/or Java issue.
Can anyone confirm this issue ?
That was a bug in 1.4.1, but should be fixed in 1.4.2