You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2024. It is now read-only.
After your last update, the #63 problem I reported was solved perfectly, and the server is running normally! I'm really excited. Thanks to the developers! But today I used the windspigot updated yesterday, there was a problem.
Describe the bug
The server will crash after running for several hours. Bug on latest
Is the bug on the latest version of WindSpigot?
Yes, it's the latest version updated yesterday.
To Reproduce
Steps to reproduce the behavior:
[17:22:14 ERROR]: The server has stopped responding!
[17:22:14 ERROR]: Please report this to WindSpigot directly!
[17:22:14 ERROR]: Be sure to include ALL relevant console errors and Minecraft crash reports
[17:22:14 ERROR]: WindSpigot version: WindSpigot Release v2.1.3 (MC: 1.8.8)
[17:22:14 ERROR]: ------------------------------
[17:22:14 ERROR]: Server thread dump (Look for plugins here before reporting to WindSpigot!):
[17:22:14 ERROR]: ------------------------------
[17:22:14 ERROR]: Current Thread: Server thread
[17:22:14 ERROR]: PID: 24 | Suspended: false | Native: false | State: WAITING
[17:22:14 ERROR]: Stack:
[17:22:14 ERROR]: java.base@11.0.15/jdk.internal.misc.Unsafe.park(Native Method)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1039)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1345)
[17:22:14 ERROR]: app//javafixes.concurrency.ReusableCountLatch.waitTillZero(ReusableCountLatch.java:120)
[17:22:14 ERROR]: app//ga.windpvp.windspigot.world.WorldTickManager.tickAsync(WorldTickManager.java:120)
[17:22:14 ERROR]: app//ga.windpvp.windspigot.world.WorldTickManager.tick(WorldTickManager.java:79)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:1087)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:451)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:959)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:730)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.lambda$spin$0(MinecraftServer.java:164)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer$$Lambda$109/0x0000000800222c40.run(Unknown Source)
[17:22:14 ERROR]: java.base@11.0.15/java.lang.Thread.run(Thread.java:829)
The text was updated successfully, but these errors were encountered:
Before I entered and the server "died" (since it does not crash, but becomes unusable, you cannot make commands, you cannot enter, in short, dead) nothing happened, the only thing that happened is that in the server in question there have been no players online for several hours.
After your last update, the #63 problem I reported was solved perfectly, and the server is running normally! I'm really excited. Thanks to the developers! But today I used the windspigot updated yesterday, there was a problem.
Describe the bug
The server will crash after running for several hours.
Bug on latest
Is the bug on the latest version of WindSpigot?
Yes, it's the latest version updated yesterday.
To Reproduce
Steps to reproduce the behavior:
[17:22:14 ERROR]: The server has stopped responding!
[17:22:14 ERROR]: Please report this to WindSpigot directly!
[17:22:14 ERROR]: Be sure to include ALL relevant console errors and Minecraft crash reports
[17:22:14 ERROR]: WindSpigot version: WindSpigot Release v2.1.3 (MC: 1.8.8)
[17:22:14 ERROR]: ------------------------------
[17:22:14 ERROR]: Server thread dump (Look for plugins here before reporting to WindSpigot!):
[17:22:14 ERROR]: ------------------------------
[17:22:14 ERROR]: Current Thread: Server thread
[17:22:14 ERROR]: PID: 24 | Suspended: false | Native: false | State: WAITING
[17:22:14 ERROR]: Stack:
[17:22:14 ERROR]: java.base@11.0.15/jdk.internal.misc.Unsafe.park(Native Method)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1039)
[17:22:14 ERROR]: java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1345)
[17:22:14 ERROR]: app//javafixes.concurrency.ReusableCountLatch.waitTillZero(ReusableCountLatch.java:120)
[17:22:14 ERROR]: app//ga.windpvp.windspigot.world.WorldTickManager.tickAsync(WorldTickManager.java:120)
[17:22:14 ERROR]: app//ga.windpvp.windspigot.world.WorldTickManager.tick(WorldTickManager.java:79)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:1087)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:451)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:959)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:730)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer.lambda$spin$0(MinecraftServer.java:164)
[17:22:14 ERROR]: app//net.minecraft.server.v1_8_R3.MinecraftServer$$Lambda$109/0x0000000800222c40.run(Unknown Source)
[17:22:14 ERROR]: java.base@11.0.15/java.lang.Thread.run(Thread.java:829)
The text was updated successfully, but these errors were encountered: