docker-minecraft-bedrock-server icon indicating copy to clipboard operation
docker-minecraft-bedrock-server copied to clipboard

1.17.40.06 server consumes all ram

Open ZippyWonderdust opened this issue 4 years ago • 1 comments

Just updated to latest version 1.17.40.06 on Ubuntu Serve 20.04 LTS. Upon start the server consumes all available ram + swap and then crashes/is killed. No errors are logged. Everything was working fine on the previous version (1.17.35). This update was just supposed to be a bug fix, right?

Anyone else having this problem? Is there a bug report at Mojang for this? Is there a workaround?

ZippyWonderdust avatar Oct 20 '21 21:10 ZippyWonderdust

A new container with that version started up fine for me and memory usage was stable:

> docker run -it --rm -e EULA=TRUE -p 19132:19132/udp itzg/minecraft-bedrock-server
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
Looking up latest version...
Downloading Bedrock server version 1.17.40.06 ...
Starting Bedrock server...
NO LOG FILE! - [] setting up server logging...
[2021-10-21 02:35:54:796 INFO] Starting Server
[2021-10-21 02:35:54:796 INFO] Version 1.17.40.06
[2021-10-21 02:35:54:796 INFO] Session ID 4902b925-81b6-4239-86b3-128175c4a0c7
[2021-10-21 02:35:54:796 INFO] Level Name: Bedrock level
[2021-10-21 02:35:54:799 INFO] Game mode: 0 Survival
[2021-10-21 02:35:54:799 INFO] Difficulty: 1 EASY
[INFO] opening worlds/Bedrock level/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 not supported
[INFO] Server started.
[INFO] IPv4 supported, port: 34649
[INFO] IPv6 not supported

From docker stats:

CONTAINER ID   NAME              CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O   PIDS
2a41eec124f6   happy_matsumoto   2.48%     311.9MiB / 12.48GiB   2.44%     64.6MB / 10.3MB   0B / 0B     28

You need to report your issue with Mojang.

itzg avatar Oct 21 '21 02:10 itzg