The server kick out players randomly and close with the message ticking entity in the crash log, I join the crash report I get each time, we don't do anything specific while it happens but it didn't happen in 15w44a for sure and we played fine with it for 2 days.
Description: Ticking entity
java.lang.NullPointerException: Ticking entity
at ry.a(SourceFile:445)
at rx.a(SourceFile:833)
at zf.a(SourceFile:634)
at rx.a(SourceFile:766)
at yw.a(SourceFile:61)
at zf.a(SourceFile:235)
at yx.a(SourceFile:148)
at we.B(SourceFile:167)
at to.e(SourceFile:121)
at th.a(SourceFile:129)
at ry.cd(SourceFile:620)
at rx.n(SourceFile:1680)
at ry.n(SourceFile:473)
at we.n(SourceFile:120)
at rx.m(SourceFile:1542)
at ry.m(SourceFile:265)
at aho.a(SourceFile:1481)
at lq.a(SourceFile:719)
at aho.g(SourceFile:1459)
at aho.k(SourceFile:1349)
at lq.k(SourceFile:552)
at net.minecraft.server.MinecraftServer.D(SourceFile:618)
at lb.D(SourceFile:314)
at net.minecraft.server.MinecraftServer.C(SourceFile:546)
at net.minecraft.server.MinecraftServer.run(SourceFile:450)
at java.lang.Thread.run(Unknown Source)Linked issues
Attachments
Comments 6
Never ever had an out of memory before, they did something in 15w44b that cause this, that server started with the first 1.9 snapshot and we are just 2 brothers on it, strictly family private server, we run a gold farm made out of nether portals and I never had the slightest problem with this, the server is running right now, my brother is AFK in the gold farm and I'm AFK in a skeleton farm with dogs killing them and no problems in 15w44a...
Stacktrace looks like MC-91786.
Please, don't assign a duplicate, I won't be notified of future updates and I'm lost when I have to follow multiple bugs and can't remember why I follow one with a title that has no relation to my bug reports.
Server is running out of memory. Assign more RAM.
This is outdated. Upgrade to 1.8U65