Minecraft Forums

---- Minecraft Crash Report ----
// Daisy, daisy...

Time: 3/25/16 11:34 AM
Description: Ticking memory connection

java.lang.NullPointerException: Ticking memory connection
at aqu.a(SourceFile:40)
at aqq.a(SourceFile:93)
at anv.a(SourceFile:161)
at ld.a(SourceFile:174)
at amy.a(SourceFile:875)
at ld.c(SourceFile:104)
at lc$a.<init>(SourceFile:39)
at lc.a(SourceFile:231)
at lc.a(SourceFile:263)
at lx.a(SourceFile:225)
at lx.c(SourceFile:277)
at lx.a(SourceFile:132)
at lo.b(SourceFile:110)
at lo.c(SourceFile:56)
at ek.a(SourceFile:221)
at ll.c(SourceFile:168)
at net.minecraft.server.MinecraftServer.B(SourceFile:625)
at net.minecraft.server.MinecraftServer.A(SourceFile:535)
at bpo.A(SourceFile:152)
at net.minecraft.server.MinecraftServer.run(SourceFile:451)
at java.lang.Thread.run(Thread.java:745)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
at aqu.a(SourceFile:40)
at aqq.a(SourceFile:93)
at anv.a(SourceFile:161)
at ld.a(SourceFile:174)
at amy.a(SourceFile:875)
at ld.c(SourceFile:104)
at lc$a.<init>(SourceFile:39)
at lc.a(SourceFile:231)
at lc.a(SourceFile:263)
at lx.a(SourceFile:225)
at lx.c(SourceFile:277)
at lx.a(SourceFile:132)
at lo.b(SourceFile:110)
at lo.c(SourceFile:56)
at ek.a(SourceFile:221)

-- Ticking connection --
Details:
Connection: [email protected]
Stacktrace:
at ll.c(SourceFile:168)
at net.minecraft.server.MinecraftServer.B(SourceFile:625)
at net.minecraft.server.MinecraftServer.A(SourceFile:535)
at bpo.A(SourceFile:152)
at net.minecraft.server.MinecraftServer.run(SourceFile:451)
at java.lang.Thread.run(Thread.java:745)

-- System Details --
Details:
Minecraft Version: 1.8.9
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 95849120 bytes (91 MB) / 258097152 bytes (246 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Profiler Position: N/A (disabled)
Player Count: 1 / 8; [lf['typhon645'/167, l='Brave New World', x=459.73, y=24.81, z=-1050.19]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.

---- Minecraft Crash Report ----
// But it works on my machine.

Time: 3/25/16 11:43 AM
Description: Exception in server tick loop

java.lang.NullPointerException: Exception in server tick loop
at awh.a(SourceFile:41)
at awd.a(SourceFile:94)
at ati.b(SourceFile:166)
at ase.a(SourceFile:803)
at ase.a(SourceFile:791)
at lo.c(SourceFile:82)
at lu.<init>(SourceFile:40)
at lv.c(SourceFile:195)
at lv.a(SourceFile:323)
at mm.a(SourceFile:907)
at byn.C(SourceFile:158)
at net.minecraft.server.MinecraftServer.run(SourceFile:457)
at java.lang.Thread.run(Thread.java:745)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- System Details --
Details:
Minecraft Version: 1.9
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 255338128 bytes (243 MB) / 419880960 bytes (400 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 99
Profiler Position: N/A (disabled)
Player Count: 1 / 8; [lr['typhon645'/40381, l='Brave New World', x=459.73, y=24.81, z=-1050.19]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.