Minecraft Server Crashes with SIGBUS Error in OpenJDK 21.0.7 (No Errors Preceding Crash)

[Chrigux]

Describe the problem

I'm encountering a fatal crash in a Minecraft server running within the itzg/docker-minecraft-server Docker image. The crash occurs with a SIGBUS (0x7) error in the Java Runtime Environment (OpenJDK 21.0.7), specifically in the VM Periodic Task Thread during the PerfLongVariant::sample() function. Notably, there are no errors or warnings in the Minecraft server logs immediately preceding the crash, but creating a hs_err_pid1.log file in the data directory. The server terminated unexpectedly after approximately 5-6 hours of uptime.

This happens very few days.

Container definition

docker run
  -d
  --name='itzg-minecraft-server'
  --net='bridge'
  --pids-limit 2048
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="server"
  -e HOST_CONTAINERNAME="itzg-minecraft-server"
  -e 'MEMORY'='8G'
  -e 'TZ'='Europe/Berlin'
  -e 'TYPE'='VANILLA'
  -e 'VERSION'='LATEST'
  -e 'MOTD'='The SVG Minecraft Server'
  -e 'DIFFICULTY'='easy'
  -e 'OVERRIDE_ICON'='FALSE'
  -e 'HARDCORE'='false'
  -e 'SEED'='499200391'
  -e 'MODE'='survival'
  -e 'SERVER_NAME'='The SVG Minecraft Server'
  -e 'CF_API_KEY'=''
  -e 'CF_PAGE_URL'=''
  -e 'CF_SLUG'=''
  -e 'ONLINE_MODE'='true'
  -e 'ENABLE_WHITELIST'='true'
  -e 'VIEW_DISTANCE'='18'
  -e 'MAX_PLAYERS'='20'
  -e 'EULA'='TRUE'
  -e 'SNOOPER_ENABLED'='false'
  -e 'SPAWN_PROTECTION'='0'
  -e 'GENERATOR_SETTINGS'=''
  -e 'LEVEL_TYPE'='minecraft:default'
  -e 'PVP'='true'
  -e 'LEVEL'='world'
  -e 'EXEC_DIRECTLY'='true'
  -e 'STOP_SERVER_ANNOUNCE_DELAY'='35'
  -e 'FABRIC_LAUNCHER_VERSION'=''
  -e 'FABRIC_LOADER_VERSION'=''
  -e 'FORGE_VERSION'=''
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://djeqr6to3dedg.cloudfront.net/repo-logos/itzg/minecraft-server/live/logo-1704684813344.png'
  -p '25565:25565/tcp'
  -p '25565:25565/udp'
  -v '/mnt/user/appdata/minecraft/':'/data':'rw'
  -v '/mnt/user/appdata/minecraft/downloads/':'/downloads':'rw'
  --health-cmd='mc-health'
  --health-interval=30s
  --health-retries=10
  --health-timeout=10s
  --health-start-period=1m 'itzg/minecraft-server'

Container logs

...
[23:41:11] [Server thread/INFO]: Disconnecting todaracmustpay (/156.146.63.209:30737): You are not white-listed on this server!
[23:41:11] [Server thread/INFO]: todaracmustpay (/156.146.63.209:30737) lost connection: You are not white-listed on this server!
[23:41:11] [Server thread/WARN]: handleDisconnection() called twice
[00:50:13] [Server thread/WARN]: handleDisconnection() called twice

No service logs after this until the crash at Fri May 16 01:17:38 2025 with the crash generating an hs_err_pid1.log file -> attachment hs_err_pid1.log

Manual restart the next day:

[19:22:14] [ServerMain/INFO]: Environment: Environment[sessionHost=https://sessionserver.mojang.com, servicesHost=https://api.minecraftservices.com, name=PROD]
[19:22:16] [ServerMain/INFO]: Loaded 1373 recipes
[19:22:16] [ServerMain/INFO]: Loaded 1484 advancements
[19:22:16] [Server thread/INFO]: Starting minecraft server version 1.21.5
...

[itzg]

This seems like something to report to Mojang. After setup of the files this image simple executes the server jar.

[BnDLett]

I'm facing a similar issue. The container doesn't crash outright, but any input to it does fail and I cannot connect to the server. I'm figuring that this could be an error relating to Docker itself as I need to restart the docker engine to be able to use Portainer properly.

Minus the netty.io spam in my logs (could be due to a mod -- I'll need to confirm), there are no further indication of what could be causing the issue. Are you experiencing any weird behavior?

[Chrigux]

I'm facing a similar issue. The container doesn't crash outright, but any input to it does fail and I cannot connect to the server. I'm figuring that this could be an error relating to Docker itself as I need to restart the docker engine to be able to use Portainer properly.

Minus the netty.io spam in my logs (could be due to a mod -- I'll need to confirm), there are no further indication of what could be causing the issue. Are you experiencing any weird behavior?

I'm fairly certain now my problem is very specific to my environment, and the cause has just maybe something to do with the docker image. Even if, that would be because of some configuration the docker makes to the JVM running the Minecraft server.

1. The JVM log I provided hints at a crash that's occurring during performance data collection inside the JVM.
2. As a workaround, I tried to disable the performance data collection with the JVM XX Option "-XX:-UsePerfData" and so far i have not crashed anymore.
3. I did not much research what consequences this has, but my server is a local very small installation and i don't want to invest any more time. So I just stick with my workaround for now.

@BnDLett as for your problem:

• If you don't have a JVM crash log with a name like "hs_err_pid1.log" in your data directory with en error/crash right at PerfLongVariant::sample(). Your problem is very likely not related to the problem I have.