-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server crashes when players are exploring (suspected mod is zeta?) #33
Comments
---- Minecraft Crash Report ---- Time: 2024-07-31 20:00:27 java.lang.Error: ServerHangWatchdog detected that a single server tick took 60.35 seconds (should be max 0.05) A detailed walkthrough of the error, its code path and all known details is as follows:-- Head -- "Finalizer" daemon prio=8 Id=10 WAITING on java.lang.ref.NativeReferenceQueue$Lock@33b9fa37 "Signal Dispatcher" daemon prio=9 Id=11 RUNNABLE "Common-Cleaner" daemon prio=8 Id=18 TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@3d7e1230 "Notification Thread" daemon prio=9 Id=19 RUNNABLE "JNA Cleaner" daemon prio=5 Id=34 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@39419147 "Timer hack thread" daemon prio=5 Id=35 TIMED_WAITING "modloading-worker-0" daemon prio=5 Id=38 WAITING on java.util.concurrent.ForkJoinPool@7c43180b "modloading-worker-0" daemon prio=5 Id=40 TIMED_WAITING on java.util.concurrent.ForkJoinPool@7c43180b "modloading-worker-0" daemon prio=5 Id=43 WAITING on java.util.concurrent.ForkJoinPool@7c43180b "Thread-1" daemon prio=5 Id=44 TIMED_WAITING "FileSystemWatchService" daemon prio=5 Id=45 RUNNABLE (in native) "ConfigSaver" daemon prio=5 Id=48 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@573df6 "ConfigSaver" daemon prio=5 Id=49 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4d75405e "Yggdrasil Key Fetcher" daemon prio=5 Id=56 TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@788b3b1e "Worker-Main-1" daemon prio=5 Id=58 TIMED_WAITING on java.util.concurrent.ForkJoinPool@1c6ce744 "Worker-Main-2" daemon prio=5 Id=59 WAITING on java.util.concurrent.ForkJoinPool@1c6ce744 "Worker-Main-3" daemon prio=5 Id=60 WAITING on java.util.concurrent.ForkJoinPool@1c6ce744 "Worker-Main-4" daemon prio=5 Id=61 WAITING on java.util.concurrent.ForkJoinPool@1c6ce744 "Worker-Main-5" daemon prio=5 Id=62 WAITING on java.util.concurrent.ForkJoinPool@1c6ce744 "Worker-Main-6" daemon prio=5 Id=63 WAITING on java.util.concurrent.ForkJoinPool@1c6ce744 "Server thread" prio=8 Id=65 RUNNABLE "DestroyJavaVM" prio=5 Id=67 RUNNABLE "Server console handler" daemon prio=8 Id=68 RUNNABLE (in native)
"Netty Epoll Server IO #0" daemon prio=8 Id=69 RUNNABLE "FileSystemWatchService" daemon prio=8 Id=70 RUNNABLE (in native) "Netty Epoll Server IO #1" daemon prio=8 Id=71 RUNNABLE (in native) "Netty Epoll Server IO #2" daemon prio=8 Id=72 RUNNABLE (in native) "Netty Epoll Server IO #3" daemon prio=8 Id=73 RUNNABLE (in native) "Netty Epoll Server IO #4" daemon prio=8 Id=74 RUNNABLE (in native) "Netty Epoll Server IO #5" daemon prio=8 Id=78 RUNNABLE (in native) "Netty Epoll Server IO #6" daemon prio=8 Id=81 RUNNABLE (in native) "Netty Epoll Server IO #7" daemon prio=8 Id=83 RUNNABLE (in native) "Server Watchdog" daemon prio=8 Id=84 RUNNABLE "LanServerPinger #1" daemon prio=8 Id=85 RUNNABLE "VoiceChatPacketProcessingThread" daemon prio=8 Id=87 RUNNABLE "VoiceChatServerThread" daemon prio=8 Id=86 RUNNABLE (in native)
"Netty Epoll Server IO #8" daemon prio=8 Id=88 RUNNABLE "Netty Epoll Server IO #9" daemon prio=8 Id=89 RUNNABLE (in native) "Netty Epoll Server IO #10" daemon prio=8 Id=90 RUNNABLE (in native) "Netty Epoll Server IO #11" daemon prio=8 Id=91 RUNNABLE (in native) "Netty Epoll Server IO #12" daemon prio=8 Id=92 RUNNABLE (in native) "Netty Epoll Server IO #13" daemon prio=8 Id=93 RUNNABLE (in native) "Netty Epoll Server IO #14" daemon prio=8 Id=94 RUNNABLE (in native) "Netty Epoll Server IO #15" daemon prio=8 Id=100 RUNNABLE (in native) Stacktrace: -- Performance stats -- -- System Details -- |
message.txt
The text was updated successfully, but these errors were encountered: