Client loads fine and loads the game to select your save. I open up the game and sticks to 68% for a bit, and then quickly after reaching 100% the game crashes every time. I have some saves from version 1.12 that also won't load.
Not sure if its relevant, but this particular world loaded on a small island surrounded with TONS of seaweed. Not sure if all that wiggling from the seaweed has any affect on this. Wasn't sure if any other actual world elements have an effect, but I haven't ventured off the island, so I wouldn't expect many chunks have been generated yet. I tried reducing all the graphics settings to minimum to see if it would help but no luck.
1.13\: [^crash-2018-07-25_15.37.21-server.txt]
---- Minecraft Crash Report ----
// Why did you do that?
Time: 7/25/18 3:37 PM
Description: Ticking memory connection
java.lang.IllegalStateException: Not a JSON Object: null
at com.google.gson.JsonElement.getAsJsonObject(JsonElement.java:90)
at wn.a(SourceFile:82)
at wn.<init>(SourceFile:48)
at vo.a(SourceFile:915)
at te.<init>(SourceFile:159)
at vo.g(SourceFile:442)
at ud.b(SourceFile:113)
at ud.Y_(SourceFile:65)
at hw.a(SourceFile:238)
at ua.c(SourceFile:171)
at net.minecraft.server.MinecraftServer.w(SourceFile:749)
at net.minecraft.server.MinecraftServer.v(SourceFile:656)
at dfx.v(SourceFile:157)
at net.minecraft.server.MinecraftServer.run(SourceFile:559)
at java.lang.Thread.run(Thread.java:748)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Server thread
Stacktrace:
at com.google.gson.JsonElement.getAsJsonObject(JsonElement.java:90)
at wn.a(SourceFile:82)
at wn.<init>(SourceFile:48)
at vo.a(SourceFile:915)
at te.<init>(SourceFile:159)
at vo.g(SourceFile:442)
at ud.b(SourceFile:113)
at ud.Y_(SourceFile:65)
at hw.a(SourceFile:238)
-- Ticking connection --
Details:
Connection: hw@3524af1
Stacktrace:
at ua.c(SourceFile:171)
at net.minecraft.server.MinecraftServer.w(SourceFile:749)
at net.minecraft.server.MinecraftServer.v(SourceFile:656)
at dfx.v(SourceFile:157)
at net.minecraft.server.MinecraftServer.run(SourceFile:559)
at java.lang.Thread.run(Thread.java:748)
-- System Details --
Details:
Minecraft Version: 1.13
Operating System: Linux (amd64) version 4.15.0-29-generic
Java Version: 1.8.0_171, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 515229120 bytes (491 MB) / 1174405120 bytes (1120 MB) up to 2147483648 bytes (2048 MB)
JVM Flags: 7 total; -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Profiler Position: N/A (disabled)
Player Count: 0 / 8; []
Data Packs: vanilla
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.Related issues
Attachments
Comments
migrated
Uriel Salischiker
Can you attach the 1.12 and 1.13 worlds?
migrated
Sorry for the delayed reply, for some reason Jira doesn't like me.
I've attached my 1.13 world, but my 1.12 world is bigger than 10mb so Jira is rejecting it.
Here's a dropbox link containing both.
migrated
Was playing around trying to see if I can get different results. I noticed when I open the launcher it says the launcher has a new version. I installed minecraft through the ubuntu repo through snap. So I tried updating through apt, and it didn't update, and I tried removing and reinstalling and it still said a launcher update was available. Since my original problem was dealing with the snap installed version, I decided to continue on rather than try out the deb file on the mojang website.
I also tried creating a new world. And loading into the world was actually successful. After trying this I retried my 1.13 and it failed like normal but when I tried my 1.12 save it loaded successfully, which just to reiterate, I tried the 1.12 save tons of times previously and it didn't work. When I first was experiencing the crashes I had pixelmon and the trecapacitator mod installed for 1.12, and when I started getting the crash I removed them from my mod folder. Perhaps the reinstall I just did removed forge and removed some part of the problem. But the 1.13 save still has the same pattern. Loads, stops at 68% for a time, continues on to 100%, shows "loading world" and then crashes. The other successful attempts I just did actually got to show "joining server" and then actually loaded the world successfully.
I've just added the world I was able to create successfully to the attachments and to my dropbox folder just in case it has any useful data.
migrated
I jsut got the same error with my 1.13 server. The server can load the world, but once a client try to enter the world, the server spilt out this internal server error.
The issure started when the computer hosting the server got a power failure.
(BTW, should i create a seperate issure for this as it happens on a server?)
migrated
Ok, I just found the corrupted file. In world/stats, if you delete the json file inside, everything will returned to normal.
It seems that for some reason, minecraft voided your stats data. If your situation is the same as mine, you should find a 0KB sized json file in world/stats. Deleting it will cause minecraft to generate a new stats json file, and therefore fixing the null json file issure.
migrated
Of cause, by deleting the stats file, your statistics will be gone, and unless you have a backup, there's no way you can recover the statistics data.
Mojang should add an exception which is when it detected an invaild file, the crash report will say where that file is, or even better, automatically generate a new one.
migrated
Also, since it seems that the same crash reports shows whenever the minecraft tried to load an invaild/corrupted json file, your cases may very well be different. If the fix doesn't work, go through your .minecraft folder and find a json file that has 0KB in it and then delete it.
migrated
Sorry for the late reply. I tried deleting the voided json file and it worked right after that. Thanks!
violine1101
Closed as a duplicate of MC-133098.