-
Bug
-
Resolution: Awaiting Response
-
None
-
Minecraft 1.14 Pre-Release 1
-
None
-
Windows 10, x64
-
Unconfirmed
When I loaded in my main survival world for the second time in prerelease 1, it crashed, and now crashes whenever i try to load it. It loads normally at first, but then crashes after it reaches 100%. I don't have this issue with any of my other worlds. If it's useful, that world that's crashing in particular is about 1.6 gigabytes. The world works again when reverting back to the last snapshop. When crashing, this message is outputted:
#
- A fatal error has been detected by the Java Runtime Environment:
# - EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffab54ca556, pid=6680, tid=0x0000000000001ed0
# - JRE version: Java(TM) SE Runtime Environment (8.0_201-b09) (build 1.8.0_201-b09)
- Java VM: Java HotSpot(TM) 64-Bit Server VM (25.201-b09 mixed mode windows-amd64 compressed oops)
- Problematic frame:
- C [msvcrt.dll+0x2a556]
# - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# - An error report file with more information is saved as:
- {path omitted}
\.minecraft\hs_err_pid6680.log
# - If you would like to submit a bug report, please visit:
- http://bugreport.java.com/bugreport/crash.jsp
#
UPDATE: While I encountered no chunk problems when I loaded the world for the first time, I noticed some chunks in my world have reset when I went back to the last snapshot, so this is probably related to those bug reports.
- relates to
-
MC-147207 hs_pid_error appears for no reason in snapshots.
- Resolved