Open nicolube opened 1 week ago
What are your startup flags? Can you enable debug and share a log file when this happens? Can you also provide a heap dump of when the issue occurs?
With no flags... just java -jar ...jar
Just keeps claiming until I kill it (10-15% is our base load...).
I am having the exact same issue. I am running the standalone on Linux (Debian). What I am noticing is that MCXboxBroadcast starts out using very little CPU and the usage climbs until it reaches 100% or if it is restarted. (I use a cron job to restart it every 8 hours). One thing to note is that I am running MCXboxBroadcast on a quad core system, and the CPU usage will only climb to 100% of a single core. (25% of the total CPU). I run the Minecraft Bedrock server on the exact same machine, but I have not really noticed any performance dips when playing on the server. My biggest concern is the excess power consumption and the fact that the physical server runs a bit hotter than normal even when no one is actively playing on the server.
I am not using any startup flags when started MCXboxBroadcast, I am just using "java -jar MCXboxBroadcastStandalone.jar"
@TylerJohnson177 My current workaround is that I restart it every 15 min using crontab....
Maybe that helps for u too until it gets fixed.
Try build 60 I've added better handling of thread cleanup so there should be less threads that sit in the background hogging resources.
I am also experiencing this issue on build 60. CPU usage is extremely high, reaches 100+% of 1 core pretty much instantly. https://paste.md-5.net/qujikowuco.rb https://paste.md-5.net/awejuhonir.bash
openjdk version "21.0.4" 2024-07-16 OpenJDK Runtime Environment (build 21.0.4+7-Ubuntu-1ubuntu224.04) OpenJDK 64-Bit Server VM (build 21.0.4+7-Ubuntu-1ubuntu224.04, mixed mode, sharing)
Using extension build #60
Startup flags: java \ -Xms4000M \ -Xmx4000M \ -XX:+UseG1GC \ -XX:G1HeapRegionSize=4M \ -XX:+UnlockExperimentalVMOptions \ -XX:+ParallelRefProcEnabled \ -XX:+AlwaysPreTouch \ -XX:MaxInlineLevel=15 \ -jar velocity.jar
Hello,
our Monitoring + htop shows extremely High CPU usage when using the latest standalone.
The drop off u see here was caused by a restart of the standalone.
Java Version:
Used Standalone: