Extremely high usage of jdk.internal.misc.Unsafe.park.
Renderthegreat opened this issue ยท 1 comments
Bug Description
While playing on my server out of nowhere the tick rate dropped to 0 tps. By pausing the server and using spark it shows that the jdk.internal.misc.Unsafe.park function was being over used.
Reproduction Steps
I have no idea
Log File
Unsafe.park indicates that the server thread is either waiting for the next tick, or waiting for a background thread to complete a task. When the async profiler is not used (as indicated by Spark in this log), it will falsely attribute time the server spends waiting as CPU time. You should look at other parts of the profile to identify what is actually causing the lag.