Major After starting the server, upon pinging the server (Seeing if its online), the server severely spams errors to the point it created a 700 MB log file (Yes, MB) in about 5 seconds from an empty log at the start.
The error(s) were this
java.lang.RuntimeException: Unable to access address of buffer
at io.netty.channel.epoll.Native.read(Native Method) ~[spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.doReadBytes(EpollSocketChannel.java:678) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.epollInReady(EpollSocketChannel.java:714) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe$3.run(EpollSocketChannel.java:755) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:268) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [spigot-1.10.jar:git-Spigot-c55900f-9af379f]
at java.lang.Thread.run(java.base@9-internal/Thread.java:804) [?:?]
[22:38:22] Netty Epoll Server IO #1/WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
