Daniel McQ
- danielmcq
- danielmcq
- America/Denver
- Yes
- No
1 issues
Key
Summary
Status
Reporter
Assignee
Created
MC-64662
Added Attachments:
Added Attachments:
Added Attachments:
Changed Description:
Playing from Mac OS X client on my world running on a server box on my local network. The server is running Linux (see Environment above). I started to attack a zombie when I noticed that everything stopped moving and the animal sounds stopped. I disconnected and tried to reconnect but only got timeout errors. I connected to the Minecraft server via ssh and used my control script to stop and start the server again. After that the connection would be refused. The first error is listed in the summary of this issue. 60 seconds later, the server logged another error of type java.lang.Thread.sleep(Native Method). I have attached both crash reports.
First crash:
java.lang.NullPointerException: Ticking entity at bou.a(SourceFile:77) at bou.a(SourceFile:65) at boy.a(SourceFile:77) at boy.a(SourceFile:37) at boy.a(SourceFile:27) at aay.a(SourceFile:71) at zl.a(SourceFile:57) at zb.a(SourceFile:72) at xl.bE(SourceFile:446) at xk.l(SourceFile:1430) at xl.l(SourceFile:316) at afc.l(SourceFile:39) at afz.l(SourceFile:203) at xk.j(SourceFile:1298) at xl.j(SourceFile:194) at afc.j(SourceFile:44) at afz.j(SourceFile:259) 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) at net.minecraft.server.MinecraftServer.y(SourceFile:606) at pk.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:530) at net.minecraft.server.MinecraftServer.run(SourceFile:446) at java.lang.Thread.run(Thread.java:745)First crash detail:
---- Minecraft Crash Report ---- // Daisy, daisy... Time: 7/30/14 11:09 PM Description: Ticking entity java.lang.NullPointerException: Ticking entity at bou.a(SourceFile:77) at bou.a(SourceFile:65) at boy.a(SourceFile:77) at boy.a(SourceFile:37) at boy.a(SourceFile:27) at aay.a(SourceFile:71) at zl.a(SourceFile:57) at zb.a(SourceFile:72) at xl.bE(SourceFile:446) at xk.l(SourceFile:1430) at xl.l(SourceFile:316) at afc.l(SourceFile:39) at afz.l(SourceFile:203) at xk.j(SourceFile:1298) at xl.j(SourceFile:194) at afc.j(SourceFile:44) at afz.j(SourceFile:259) 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) at net.minecraft.server.MinecraftServer.y(SourceFile:606) at pk.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:530) at net.minecraft.server.MinecraftServer.run(SourceFile:446) 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 bou.a(SourceFile:77) at bou.a(SourceFile:65) at boy.a(SourceFile:77) at boy.a(SourceFile:37) at boy.a(SourceFile:27) at aay.a(SourceFile:71) at zl.a(SourceFile:57) at zb.a(SourceFile:72) at xl.bE(SourceFile:446) at xk.l(SourceFile:1430) at xl.l(SourceFile:316) at afc.l(SourceFile:39) at afz.l(SourceFile:203) at xk.j(SourceFile:1298) at xl.j(SourceFile:194) at afc.j(SourceFile:44) at afz.j(SourceFile:259) at aqh.a(SourceFile:1410) at qo.a(SourceFile:601) at aqh.g(SourceFile:1388) -- Entity being ticked -- Details: Entity Type: Zombie (afz) Entity ID: 268763 Entity Name: Zombie Entity's Exact location: 123.50, 63.00, 1534.22 Entity's Block location: 123.00,63.00,1534.00 - World: (123,63,1534), Chunk: (at 11,3,14 in 7,95; contains blocks 112,0,1520 to 127,255,1535), Region: (0,2; contains chunks 0,64 to 31,95, blocks 0,0,1024 to 511,255,1535) Entity's Momentum: -0.31, 0.36, -0.25 Entity's Rider: ~~ERROR~~ NullPointerException: null Entity's Vehicle: ~~ERROR~~ NullPointerException: null Stacktrace: at aqh.i(SourceFile:1281) at qo.i(SourceFile:479) -- Affected level -- Details: Level name: Furya All players: 1 total; [qr['danielmcq'/163, l='Furya', x=125.01, y=63.00, z=1535.46]] Chunk stats: ServerChunkCache: 1592 Drop: 0 Level seed: 973714163 Level generator: ID 00 - default, ver 1. Features enabled: true Level generator options: Level spawn location: 8.00,64.00,-28.00 - World: (8,64,-28), Chunk: (at 8,4,4 in 0,-2; contains blocks 0,0,-32 to 15,255,-17), Region: (0,-1; contains chunks 0,-32 to 31,-1, blocks 0,0,-512 to 511,255,-1) Level time: 174777729 game time, 5826720 day time Level dimension: 0 Level storage version: 0x04ABD - Anvil Level weather: Rain time: 4581 (now: true), thunder time: 99128 (now: false) Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false Stacktrace: at net.minecraft.server.MinecraftServer.y(SourceFile:606) at pk.y(SourceFile:303) at net.minecraft.server.MinecraftServer.x(SourceFile:530) at net.minecraft.server.MinecraftServer.run(SourceFile:446) at java.lang.Thread.run(Thread.java:745) -- System Details -- Details: Minecraft Version: 14w31a Operating System: Linux (amd64) version 3.2.0-4-amd64 Java Version: 1.7.0_65, Oracle Corporation Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 880212888 bytes (839 MB) / 1215299584 bytes (1159 MB) up to 1431830528 bytes (1365 MB) JVM Flags: 2 total; -Xmx1536M -Xms1024M IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Player Count: 1 / 5; [qr['danielmcq'/163, l='Furya', x=125.01, y=63.00, z=1535.46]] Is Modded: Unknown (can't tell) Type: Dedicated Server (map_server.txt)
I've found that I can get a converted 32x texture pack to work on the first load without distorting the fonts. However, after closing and re-opening MineCraft, the glitch shows up again, even with the default pack. The workaround for me has been to delete any resource packs found in the resource pack folder before opening MineCraft, then copy over the converted hi-res pack to the proper folder, then select it within MineCraft, and it works just fine.
Because of this behavior I'm questioning what Grum has said about this not being a bug, since the hi-res fonts do in fact work after jumping through some hoops.
I think this was resolved in MC-13754.
Attempted to reproduce in 1.6.1 in Creative Mode. Spawned a horse with an egg, tamed it, put a name on a name tag, then applied it to the horse. After the horse had the name from the tag, logged out, then logged back in. The horse was still there. Problem didn't appear to exist.
I can confirm that this is still a problem in 13w47e. It seems to be that all of the hotkeys and other inventory type shortcuts don't work while mounted on a horse, donkey, or mule.
This is definitely happening to me in 14w11b with both chickens and cows (haven't tested with pigs). My chickens have a smaller enclosure (2x2) and die more frequently (during gameplay, probably when chunk gets unloaded then loaded). The cows' enclosure is a larger one (approx 8x15) and they seem to only die when I log back into my world.
Happened to me when entering world. Attaching my crash report.
It seems that signs can cause this error to occur, too. I was able to move my character to the nether where I had no item frames, but when I looked at a sign, the game crashed.
Affects 14w19a on OS X Mavericks, 64 bit Oracle JVM. Crash report attached.
Happened to me again. In the same environment as last time. Both the previous time and this time I was simply moving around my world, and it seems as though chunks were still loading as I looked around when the crash occurred. The previous incident was in survival mode with a normally generated world. This instance was in creative mode in a flat desert world.
Is this still an issue as of 14w31a? @Dinnerbone made pathfinding multi-threaded, which might address the performance of it.
This relates to
MC-63590@Anthony Martin I never really saw this issue before but I agree that it seems to be worse in this latest snapshot (14w31a). My server crashed and I believe it was caused by pathfinding threads going crazy. See
MC-64662I personally haven't seen it happen again as I update my snapshots. I currently have my server running on 1.8-pre2 and things are still running smoothly without anymore crashes.
Confirmed on 1.8
My guess is the problem is related to rounding errors and/or the hit box of the mobs.
Probably what happens is their location gets saved with a very precise floating point number and then when the chunk they're in gets re-loaded, that number gets rounded to something less precise and the mob is moved and they end up in a solid block or on the other side of a fence. The other thing could be that their hit box overlaps with other mobs and there's some sort of algorithm which attempts to keep all mobs a certain distance apart and their location is put to one of those unfavorable locations. The problem could also be a problem of those two things.
Just my two cents.