C2ME-fabric
C2ME-fabric copied to clipboard
TPS slow down followed by OOM crash
Describe the bug I run a dedicated server for my friends and I. For a few days, no one had been on the server, but the classic "Can't keep up! Is the server overloaded?" message started getting recorded in the logs every minutes... and then every few seconds... until finally C2ME crashed the server with an OOM error.
To Reproduce Steps to reproduce the behavior:
- Run the server
-
java -Xmx12288M -Xms12288M -XX:+AlwaysPreTouch -XX:+DisableExplicitGC -XX:+ParallelRefProcEnabled -XX:+PerfDisableSharedMem -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1HeapRegionSize=8M -XX:G1HeapWastePercent=5 -XX:G1MaxNewSizePercent=40 -XX:G1MixedGCCountTarget=4 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1NewSizePercent=30 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:G1ReservePercent=20 -XX:InitiatingHeapOccupancyPercent=15 -XX:MaxGCPauseMillis=200 -XX:MaxTenuringThreshold=1 -XX:SurvivorRatio=32 -jar server.jar nogui
-
- Wait for a few days with no one online
Expected behavior No slow down or crash.
Runtime info (please complete the following information):
- OS: Debian 10
- Minecraft version: 1.20.6
- Mod version: 0.2.0+alpha.11
Crash reports / logs
- 2024-06-03-2.log
- 2024-06-05-1.log
- 2024-06-07-1.log
- 2024-06-08-1.log
- 2024-06-09-1.log
- 2024-06-10-1.log
- 2024-06-14-1.log
- 2024-06-15-1.log
- latest.log
It should be noted that everything past [17:43:39]
did not get recorded in the latest.log
file. I had to manually copy it from the Debian console and paste it into the file.
For privacy, player names, UUIDs, IP addresses, and chats have been redacted.
Other mods
- AntiXray
- Debugify
- Fabric API
- FerriteCore
- Geyser
- Krypton
- Lithium
- Memory Leak Fix
- ModernFix
- Noisium
- Whiteout
Checklist
- [x] I am using the official version of the mod.
- [ ] I tried the latest development version but the issue persists.
- [x] I searched for similar open issues and could not find an existing bug report on this.