SteamWar/FightSystem
Archiviert
13
1

Chunkhider-Bug #65

Geschlossen
2019-12-08 17:42:03 +01:00 von Lixfel geöffnet · 1 Kommentar
Besitzer

[17:20:10] [Protocol Worker #14 - FightSystem - [recv: , send: MAP_CHUNK[class=PacketPlayOutMapChunk, id=34]]/WARN]: [FightSystem] Plugin FightSystem v1.0 generated an exception while executing task 60
io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 14579 byte(s) of direct memory (used: 2075907682, max: 2075918336)
at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:640) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:594) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledUnsafeNoCleanerDirectByteBuf.java:30) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledByteBufAllocator.java:186) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.(UnpooledUnsafeDirectByteBuf.java:68) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.(UnpooledUnsafeNoCleanerDirectByteBuf.java:25) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeNoCleanerDirectByteBuf.(UnpooledByteBufAllocator.java:181) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.UnpooledByteBufAllocator.newDirectBuffer(UnpooledByteBufAllocator.java:91) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:185) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:176) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at de.steamwar.fightsystem.utils.TechHider$3.onPacketSending(TechHider.java:144) ~[?:?]
at com.comphenix.protocol.async.AsyncListenerHandler.processPacket(AsyncListenerHandler.java:640) ~[?:?]
at com.comphenix.protocol.async.AsyncListenerHandler.listenerLoop(AsyncListenerHandler.java:596) ~[?:?]
at com.comphenix.protocol.async.AsyncListenerHandler.access$200(AsyncListenerHandler.java:48) ~[?:?]
at com.comphenix.protocol.async.AsyncListenerHandler$2.run(AsyncListenerHandler.java:229) ~[?:?]
at com.comphenix.protocol.async.AsyncListenerHandler$3.run(AsyncListenerHandler.java:300) ~[?:?]
at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftTask.run(CraftTask.java:76) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:52) [spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_211]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_211]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_211]

[17:20:10] [Protocol Worker #14 - FightSystem - [recv: , send: MAP_CHUNK[class=PacketPlayOutMapChunk, id=34]]/WARN]: [FightSystem] Plugin FightSystem v1.0 generated an exception while executing task 60 io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 14579 byte(s) of direct memory (used: 2075907682, max: 2075918336) at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:640) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:594) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledUnsafeNoCleanerDirectByteBuf.java:30) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledByteBufAllocator.java:186) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.UnpooledUnsafeDirectByteBuf.<init>(UnpooledUnsafeDirectByteBuf.java:68) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.<init>(UnpooledUnsafeNoCleanerDirectByteBuf.java:25) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeNoCleanerDirectByteBuf.<init>(UnpooledByteBufAllocator.java:181) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.UnpooledByteBufAllocator.newDirectBuffer(UnpooledByteBufAllocator.java:91) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:185) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:176) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at de.steamwar.fightsystem.utils.TechHider$3.onPacketSending(TechHider.java:144) ~[?:?] at com.comphenix.protocol.async.AsyncListenerHandler.processPacket(AsyncListenerHandler.java:640) ~[?:?] at com.comphenix.protocol.async.AsyncListenerHandler.listenerLoop(AsyncListenerHandler.java:596) ~[?:?] at com.comphenix.protocol.async.AsyncListenerHandler.access$200(AsyncListenerHandler.java:48) ~[?:?] at com.comphenix.protocol.async.AsyncListenerHandler$2.run(AsyncListenerHandler.java:229) ~[?:?] at com.comphenix.protocol.async.AsyncListenerHandler$3.run(AsyncListenerHandler.java:300) ~[?:?] at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftTask.run(CraftTask.java:76) ~[spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:52) [spigot-1.12.2.jar:git-Spigot-79a30d7-acbc348] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_211] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_211] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_211]
Autor
Besitzer

Was hat da nur den RAM gefressen (offensichtlich ein sehr stark laggendes Schiff (2GB RAM!)

Was hat da nur den RAM gefressen (offensichtlich ein sehr stark laggendes Schiff (2GB RAM!)
Lixfel hat diesen Issue 2019-12-10 18:36:41 +01:00 geschlossen
Dieses Repo ist archiviert. Du kannst Issues nicht kommentieren.
Keine Beschreibung angegeben.