I was walking around my rabbit farm and all of a sudden i crashed. each time i try and load that world it just crashes now. i opened the world in an older snapshot and i was able to get on but all the rabbits were acting as if they were tamed wolfs and were teleporting to me.
Looking at the crash notes it seemed to be caused by the rabbits as it said
Description: Ticking entity
java.lang.NullPointerException: Ticking entity
at aay.k(SourceFile:174)
at xl.bE(SourceFile:450)
at xk.l(SourceFile:1430)
at xl.l(SourceFile:316)
at wn.l(SourceFile:126)
at abr.l(SourceFile:38)
at acc.l(SourceFile:258)
at xk.j(SourceFile:1298)
at xl.j(SourceFile:194)
at aqh.a(SourceFile:1410)
at qo.a(SourceFile:601)
at aqh.g(SourceFile:1388)
at aqh.i(SourceFile:1281)
at qo.i(SourceFile:479)
...
-- Entity being ticked --
Details:
Entity Type: Rabbit (acc)
Entity ID: 371
Entity Name: Rabbit
Entity's Exact location: 52.32, 64.00, -5.26"Environment
– System Details –
Details:
Minecraft Version: 14w31a
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_45, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 719919336 bytes (686 MB) / 1086324736 bytes (1036 MB) up to 3817865216 bytes (3641 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx4G
IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
Profiler Position: N/A (disabled)
Player Count: 1 / 8; [qr['firehill56'/183, l='MEH!', x=40.79, y=64.00, z=15.49]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Linked issues
is duplicated by 1
Attachments
Comments 3
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Please attach the complete crash report.