[Crash]: Server crash because of a memory leak and CPU going WILD for no reasons
LeLexaas opened this issue · 5 comments
Possible Fixes
Yes
Modpack Version
1.1.0
What happened?
Hello !
I have for some time an ATM 8 server, we never had problems with it, but since the 1.1.0 modpack upgrade, we have memory leaks and the CPU running at max for no reason. It makes it all laggy and the watchdog crashes the server because it wont respond since all resources are taken.
The lifetime of the server is around 1h30, then it crashes, in an infinite loop.
It doesn't matter if anyone is on the server or not (though there is some chunks loaded)
We've had 45 crash reports since we updated (4 days ago), the last one (30mins ago) crashed for an oom, and crashed again of the watchdog because it took more than a minute to generate the crash report.. LOL
I attached both crash reports with gist.
Crash Log
https://gist.github.com/LeLexaas/c850d69de4334699e922f388beedd196
Can confirm aswell. Noticed that a few minutes before the crashes that the server is getting more and more laggy and skipping more and more ticks.
[23Dec2023 23:09:39.208] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3429ms or 68 ticks behind [23Dec2023 23:10:02.739] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2959ms or 59 ticks behind [23Dec2023 23:10:21.228] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3498ms or 69 ticks behind [23Dec2023 23:10:48.139] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2709ms or 54 ticks behind [23Dec2023 23:11:16.442] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2763ms or 55 ticks behind [23Dec2023 23:11:35.520] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3190ms or 63 ticks behind [23Dec2023 23:11:58.913] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2784ms or 55 ticks behind [23Dec2023 23:12:19.201] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2921ms or 58 ticks behind [23Dec2023 23:12:36.194] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2014ms or 40 ticks behind [23Dec2023 23:12:56.083] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3104ms or 62 ticks behind [23Dec2023 23:13:17.872] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3592ms or 71 ticks behind [23Dec2023 23:13:38.973] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 2793ms or 55 ticks behind [23Dec2023 23:13:57.759] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3829ms or 76 ticks behind [23Dec2023 23:14:17.147] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3068ms or 61 ticks behind [23Dec2023 23:14:39.868] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 7739ms or 154 ticks behind [23Dec2023 23:15:12.635] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 17805ms or 356 ticks behind [23Dec2023 23:15:46.131] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 18501ms or 370 ticks behind [23Dec2023 23:16:04.608] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 3478ms or 69 ticks behind [23Dec2023 23:16:36.071] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 16492ms or 329 ticks behind [23Dec2023 23:16:58.959] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 7929ms or 158 ticks behind [23Dec2023 23:17:43.609] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 29679ms or 593 ticks behind [23Dec2023 23:18:24.786] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 26206ms or 524 ticks behind [23Dec2023 23:19:05.353] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 25573ms or 511 ticks behind [23Dec2023 23:20:10.374] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 50044ms or 1000 ticks behind [23Dec2023 23:21:59.392] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 94062ms or 1881 ticks behind [23Dec2023 23:24:36.695] [Server thread/WARN] [net.minecraft.server.MinecraftServer/]: Can't keep up! Is the server overloaded? Running 142316ms or 2846 ticks behind
I was having this issue on my server, I narrowed it down to the AECapFix mod. It was making some stuff in Powah stuff run wild. Disabling this on my server fixed it. Whatever it is doing, it is causing memory leaks. Hopefully this helps others as it took me several hours fixing
I disabled the AECapFix mod and it's working nicely since then ! Thanks a lot for the workaround !
Though I'm curious, what did you use to find the problem ?
AECapFix leak reported to mod author via Discord DM, they've now fixed it and are working on a release version.
Talked to the mod author and we were testing out the dev version of the mod they gave me on our server. Looking much better with that. Been running it for almost 2 days without any issues.
I disabled the AECapFix mod and it's working nicely since then ! Thanks a lot for the workaround !
Though I'm curious, what did you use to find the problem ?
Eclipse Memory Analyzer