mojira.dev
MC-75059

Possible chunk corruption - crash bug

My server has an error/crash bug. It appears to affect a particular part of the world. It took me a while to figure this out as the anomaly/glitch/whatever was in the spawn chunks. Moving the spawn point several hundred meters away fixed the problem EXCEPT when the glitched area is loaded.

Futhermore, I have tracked the location and last known direction of movement of player entities when crashes occur and charted them. From this data, it looks like this crash happens when the affected chunk or chunks load(s) or unload(s). I believe this to be a sort of world file, chunk, or block corruption.

I currently have no other information about the nature or cause of this corruption.

This issue began affecting the server immediately after updating to release 1.8

There are two distinctly different errors in the enclosed crash logs, and they appear to alternate.

Related issues

Attachments

Comments

migrated
[media][media][media][media][media][media]
migrated

Dupe of MC-12949 / MC-63590

migrated

One of the errors affecting the server appears to be similar to MC-63590. However, the lava.lang.outOfMemoryError does not appear to be the same as MC-12949 according to the logs. Is the difference in the logs a result of a different minecraft version?

kumasasa

JVM Flags: 2 total; -Xmx512M -Xms512M

512M is too less for a server, see http://minecraft.gamepedia.com/Server/Requirements

Maybe related:

Java Version: 1.7.0_45, Oracle Corporation

Your Java version is out of date! Please update your Java to the latest version (1.7.0_72 / 1.8.0_25): http://www.java.com/en/download/.

  • When using a 32-bit browser on a 64-bit operating system the automatic version detection will only show the 32-bit version of Java, the 64-bit version needs to be downloaded manually: http://www.java.com/en/download/manual.jsp.

migrated

(Unassigned)

Unconfirmed

Minecraft 1.8, Minecraft 1.8.1

Retrieved