U
/u/AffectionatePhoto395
Guest
I’m currently running:
I’m running into a server freeze that seems to happen when a player gets kicked and the quit / disconnect process begins.
In the watchdog dump, the main thread is stuck in
From what I can tell, the sequence is:
Right now I’m trying to figure out whether this is more likely to be:
Has anyone seen this before?
Especially anything involving:
Relevant log snippet: https://mclo.gs/m75M5AK
submitted by /u/AffectionatePhoto395
[link] [comments]
Continue reading...
- Paper 1.21.4
- Java 21
- CMI 9.7.11.1
- CMILib 1.5.4.1
- Vulcan 2.9.7.2
- DecentHolograms 2.8.14
- PlaceholderAPI 2.11.6
I’m running into a server freeze that seems to happen when a player gets kicked and the quit / disconnect process begins.
In the watchdog dump, the main thread is stuck in
BLOCKED state, and the stack consistently points to CMI hologram cleanup during PlayerQuitEvent:CMIHologram.getLastHoloInRangeHologramManager.removeLastHologramInRangeHologramListener.onPlayerQuitEvent
From what I can tell, the sequence is:
- a player gets kicked by Vulcan
- the disconnect / quit process starts
- CMI hologram cleanup runs
- the server freezes and watchdog begins reporting it
Right now I’m trying to figure out whether this is more likely to be:
- a broken / malformed hologram
- too many stacked holograms in one area
- or some kind of lock issue in CMI hologram cleanup when players quit
Has anyone seen this before?
Especially anything involving:
PlayerQuitEvent- player kicks
- hologram cleanup on logout
- the main thread getting stuck in
BLOCKEDstate
Relevant log snippet: https://mclo.gs/m75M5AK
submitted by /u/AffectionatePhoto395
[link] [comments]
Continue reading...