-
Bug
-
Resolution: Invalid
-
None
-
1.16.1
-
None
-
Ubuntu 18.04 w/ server 1.16.1 (vanilla), 8GB RAM, Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz, openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-8u252-b09-1~18.04-b09), OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)
java -Xmx6144M -Xms6144M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalPacing -XX:ParallelGCThreads=2 -XX:+AggressiveOpts -jar server.jar nogui
Windows 10 Pro version 2004/19041.330 w/ client 1.16.1 (vanilla), 16 GB RAM, Intel Core i7-10750W 2.60GHzUbuntu 18.04 w/ server 1.16.1 (vanilla), 8GB RAM, Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz, openjdk version "1.8.0_252" OpenJDK Runtime Environment (build 1.8.0_252-8u252-b09-1~18.04-b09), OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode) java -Xmx6144M -Xms6144M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalPacing -XX:ParallelGCThreads=2 -XX:+AggressiveOpts -jar server.jar nogui Windows 10 Pro version 2004/19041.330 w/ client 1.16.1 (vanilla), 16 GB RAM, Intel Core i7-10750W 2.60GHz
-
Unconfirmed
-
(Unassigned)
Ever since upgrading from 1.15 to 1.16, after a couple days of running, the server CPU spikes to 100%+ and becomes unresponsive causing "Something's taking too long!" and ticks in excess of many seconds. Setting the watchdog timeout to -1 results in ticks in excess of a minute.
Clients cannot connect to the server and timeout while trying to connect.