I was exploring a world in creative mode before the game crashed back to the launcher with this error log.
Re-entering the world causes an immediate crash, suggesting some form of chunk/world corruption.
World Seed: 6119009283623993622
Generated in 18w50a
This has not been a consistent issue for me, and as of so far has been exclusive to this world.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000058e3dda0, pid=11824, tid=14384
#
# JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V [jvm.dll+0xadda0]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#Attachments
Comments 4
With all due respect, as I have already said, this issue is specific to this world. I highly doubt that this is down to my own hardware. I would test this seed on another machine but I only own one PC
If I'm incorrect here, then I apologise but this appears to be down to a world generation bug more than anything else.
I found another more conventional crash log that was generated in a separate crash on the same world. I have attached it.
Cannot reproduce, the world is generating fine for me, even if there is still MC-139717
The spawn is a normal jungle
Thank you for your report!
However, this issue has been closed as Invalid.
This is a technical support issue; this site is for bug reports only. We do not have the resources to provide you with technical support.
Please contact the community support, linked below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki