mirror of
https://github.com/NATroutter/egg-hytale.git
synced 2026-03-01 11:21:13 +03:00
[Bug]: CPU maxes out, causes crash every time #33
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @uponminiature on GitHub (Jan 21, 2026).
Panel Type
Pelican Panel
Panel Version
v1.0.0-beta31
Wings Version
v1.0.0-beta22
Panel Deployment Method
Docker
Wings Deployment Method
Docker
Wings Location
Same machine (Local)
Server Architecture
x86_64 (amd64)
When does the issue occur?
While server is running
Is the issue reproducible?
Yes, it happens every time
Bug Description
I'm not sure whether this is normal behaviour, but I crash almost every time with only one player joining because the CPU gets maxed out. At first, I tried setting core limits (400, 600, then 800), but it didn't help. Then I just removed the limits, and below is what happens:
And tested it a second time for good measure:
So... the Hytale server (as soon as one player joins) fully utilises the CPU, no matter if a limit is set or not, and then crashes.
It's really a bummer, everything works up to the point of launching the server. I was planning on playing with friends, but that plan's really out the window if not even I can play solo without maxing out the CPU.
For context, I'm doubting this is normal because this same server has run heavily modded Minecraft servers with 2-4 people with the CPU limit at 400.
Console Logs
Additional Context
Server fastfetch:
Docker version:
Pre-submission Checklist
@NATroutter commented on GitHub (Jan 21, 2026):
This doesn't seem like its an issue with the egg more like plugin / hytale server software issue but i can still try to help best as i can
@uponminiature commented on GitHub (Jan 22, 2026):
Force Network Flushcauses it to crash immediately.-XX:+UseCompressedOops -XX:+UseCompressedClassPointers -XX:-UseCompactObjectHeaders -XX:+UseG1GC -XX:+UseStringDeduplication -Xlog:aot@uponminiature commented on GitHub (Jan 22, 2026):
I've tried to diagnose the issue with a clean slate and no limits:
https://raw.githubusercontent.com/NATroutter/egg-hytale/refs/heads/main/egg-hytale.pelican.json. Result:Imported 1 of 1 eggsHytale100.80.0.1:31000(Attached directly to the Tailscale IP)Hytale(left default egg configuration)This time, I noticed something. Without limits, It used nearly all of my CPU for an extended period of time, but then stopped. And after that, it worked at lower CPU usage (20-600). However, memory stayed utilised at a high amount (9GB).
Context: the difference between "start" and "active" is that the active window started when I joined on one account. Also, you can see it dropped heavily at the end, I was actually still in the server by then (but standing still). The server has this window of high CPU usage but then it stops.
So this time, I can actually play after letting it use all my cores for a bit. It's weird, I don't know if it's normal.
For instance, these are the CPU stats of me joining the server (and running around a bit) after the extended period of my CPU being maxed out by the Hytale server:
@NATroutter commented on GitHub (Jan 22, 2026):
I think this might just be the server software's fault (HytaleServer.jar) what i have looked thru code and tested running servers on multiple different systems its clear that the software at this point is really bad and not optimized at all
@uponminiature commented on GitHub (Jan 22, 2026):
I see. I hope server optimisation is a priority for the Hytale dev team, it's slightly misleading how all of the online "dedicated server requirements" (i.e., 4 cores, 4GB ram), seem to be inaccurate, at least in my testing.
@NATroutter commented on GitHub (Jan 22, 2026):
After some more research i got one possible reason that could cause these issues it may be that the wings is deployed as docker container, you could try to run the server directly on the machine and see if same issue happens
@uponminiature commented on GitHub (Jan 22, 2026):
That could be the case; I've never deployed Wings outside of Docker, I may give it a go in a bit if it's straightforward on NixOS and monitor system stats.
@FeedTheChunk commented on GitHub (Jan 22, 2026):
I have wings and panel installed on bare metal with 2 other Minecraft servers running and I don't have any issues with HIGH CPU usage for what it's worth.