InventivetalentDev / MapManager

MIT License
54 stars 20 forks source link

Error on server start #58

Closed TheNety closed 4 years ago

TheNety commented 4 years ago

What steps will reproduce the problem?

  1. Start server

What were you expecting to happen? What happened instead?

This error occured on server start

[22:37:55 WARN]: [MapManager] Task #1731 for MapManager v1.7.8-SNAPSHOT generated an exception java.util.ConcurrentModificationException: null at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) ~[?:1.8.0_112] at java.util.ArrayList$Itr.next(ArrayList.java:851) ~[?:1.8.0_112] at org.inventivetalent.mapmanager.MapSender.sendMap(MapSender.java:71) ~[?:?] at org.inventivetalent.mapmanager.MapSender$1.run(MapSender.java:57) ~[?:?] at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftTask.run(CraftTask.java:84) ~[patched_1.15.2.jar:git-Paper-333] at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:461) ~[patched_1.15.2.jar:git-Paper-333] at net.minecraft.server.v1_15_R1.MinecraftServer.b(MinecraftServer.java:1256) ~[patched_1.15.2.jar:git-Paper-333] at net.minecraft.server.v1_15_R1.DedicatedServer.b(DedicatedServer.java:430) ~[patched_1.15.2.jar:git-Paper-333] at net.minecraft.server.v1_15_R1.MinecraftServer.a(MinecraftServer.java:1173) ~[patched_1.15.2.jar:git-Paper-333] at net.minecraft.server.v1_15_R1.MinecraftServer.run(MinecraftServer.java:962) ~[patched_1.15.2.jar:git-Paper-333] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]

What version of the plugin are you using?

1.7.8-SNAPSHOT

What Spigot version are you using?

Latest build of Paper 1.15.2

Did your client crash?

No

issue-label-bot[bot] commented 4 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.98. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

stale[bot] commented 4 years ago

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.