本帖最后由 YinDang 于 2021-2-23 09:02 编辑

每次出现这个报错 玩家进入子服后一切换世界就会被t到登录服

重启一遍又好了 很迷 目前是个人怀疑BungeeKick的问题,但又没办法证实,因为重启一遍好了后 过几天才会出现类似问题

补充：共有A B C D E   5个子服 玩家进入A子服切换场景才有这种问题 其他子服没有事  而且不需重启A子服 只重启bc端就会好

bc端只安装了这些插件AntiAttackRL,BungeeKick,ColorMOTD,SkinsRestorer



io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 16777216 byte(s) of direct memory (used: 939524096, max: 954728448)
    at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:775)
    at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:730)
    at io.netty.buffer.PoolArena$DirectArena.allocateDirect(PoolArena.java:645)
    at io.netty.buffer.PoolArena$DirectArena.newChunk(PoolArena.java:621)
    at io.netty.buffer.PoolArena.allocateNormal(PoolArena.java:204)
    at io.netty.buffer.PoolArena.tcacheAllocateNormal(PoolArena.java:188)
    at io.netty.buffer.PoolArena.allocate(PoolArena.java:138)
    at io.netty.buffer.PoolArena.reallocate(PoolArena.java:288)
    at io.netty.buffer.PooledByteBuf.capacity(PooledByteBuf.java:118)
    at io.netty.buffer.AbstractByteBuf.ensureWritable0(AbstractByteBuf.java:307)
    at io.netty.buffer.AbstractByteBuf.ensureWritable(AbstractByteBuf.java:282)
    at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1105)
    at io.netty.handler.codec.ByteToMessageDecoder$1.cumulate(ByteToMessageDecoder.java:99)
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:274)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
    at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
    at java.lang.Thread.run(Unknown Source)

检查一下BC端分配的内存是否太多或者太少
重新分配一下

ksconfig.yml (367 Bytes, 下载次数: 2)
刚才看了一下  不知道什么时候生成的一个这个

我看了下分配内存最大1g 我改成3g试试

因为这个问题不是立马就会好

过几天如果没事了 我会给最佳的

抱歉  我并不知道这个是什么插件的配置

从你的报错上看就是内存 的问题
好像不够
failed to allocate 16777216 byte(s) of direct memory (used: 939524096, max: 954728448)
（谷歌翻译一下就知道了

不是 这个是生成在bc里的 你敢信