Meteor spawn makes server unresponsive and crash

Issue #7 closed
Former user created an issue

Version: Spigot 1.8.8 Latest plugin version.

Meteor spawn makes the server completely unresponsive.

Error in console:

[10:18:27] [Server thread/INFO]: [0;37;1m[[0;36;1mMeteorLoot[0;37;1m] [0;37;1mThe next meteor will land in 1 minute(s)![m
[10:19:16] [Server thread/INFO]: GriefPrevention: monkeynator placed a sign @ world: x-2431, z3023;Welcome
[10:19:55] [User Authenticator #11/INFO]: UUID of player xDakotax is 384571a5-254a-4c3a-b682-bfd45db3c797
[10:20:10] [User Authenticator #12/INFO]: UUID of player xDakotax is 384571a5-254a-4c3a-b682-bfd45db3c797
[10:20:35] [Spigot Watchdog Thread/ERROR]: The server has stopped responding!
[10:20:35] [Spigot Watchdog Thread/ERROR]: Please report this to http://www.spigotmc.org/
[10:20:35] [Spigot Watchdog Thread/ERROR]: Be sure to include ALL relevant console errors and Minecraft crash reports
[10:20:35] [Spigot Watchdog Thread/ERROR]: Spigot version: git-Spigot-fdc1440-53fac9f (MC: 1.8.8)
[10:20:35] [Spigot Watchdog Thread/ERROR]: ------------------------------
[10:20:35] [Spigot Watchdog Thread/ERROR]: Server thread dump (Look for plugins here before reporting to Spigot!):
[10:20:35] [Spigot Watchdog Thread/ERROR]: ------------------------------
[10:20:35] [Spigot Watchdog Thread/ERROR]: Current Thread: Server thread
[10:20:35] [Spigot Watchdog Thread/ERROR]:     PID: 16 | Suspended: false | Native: false | State: RUNNABLE
[10:20:35] [Spigot Watchdog Thread/ERROR]:     Stack:
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.World.isValidLocation(World.java:286)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.World.a(World.java:298)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.World.isLoaded(World.java:294)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.World.getBiome(World.java:240)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         org.bukkit.craftbukkit.v1_8_R3.CraftWorld.getBiome(CraftWorld.java:600)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         org.bukkit.craftbukkit.v1_8_R3.block.CraftBlock.getBiome(CraftBlock.java:293)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.utils.LocationUtil.safeLocation(LocationUtil.java:31)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.utils.LocationUtil.getRandomLocation(LocationUtil.java:51)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.utils.LocationUtil.getMeteorCrashLocation(LocationUtil.java:38)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.meteor.Meteor.startMeteorCrash(Meteor.java:60)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.handlers.TimeHandler.reduceDropTimes(TimeHandler.java:79)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.handlers.TimeHandler.access$0(TimeHandler.java:70)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         me.blahberrys.meteorloot.handlers.TimeHandler$1.run(TimeHandler.java:47)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftTask.run(CraftTask.java:71)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:350)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:722)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:374)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:653)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:556)
[10:20:35] [Spigot Watchdog Thread/ERROR]:         java.lang.Thread.run(Thread.java:745)

Comments (2)

  1. BlahBerrys repo owner

    Thank you for taking the time to use the Issue Tracker, this issue has been solved in v1.8.5 - you can expect the release within a couple of days!

    Sincerely, BlahBerrys

  2. Log in to comment