Skip to main content

Understanding Crash Reports

Crash reports can be lengthy and complex, but key sections provide crucial information for diagnosing the issue.

Key Sections of a Crash Report

  1. Description:

    • The top section provides a brief description of the crash, often including the error message or exception that caused the crash.

  2. Time:

    • The timestamp of when the crash occurred.

  3. System Details:

    • Information about the server’s environment, including Java version, operating system, and memory allocation.

  4. Stack Trace:

    • A detailed trace of the code execution at the time of the crash, showing the exact sequence of method calls that led to the crash.

  5. Loaded Mods:

    • A list of all the mods and their versions that were loaded at the time of the crash.

Example Crash Report

---- Minecraft Crash Report ----
// Ouch. That hurt :(

Time: 7/31/24 5:15 PM
Description: Exception in server tick loop

java.lang.NullPointerException: Exception in server tick loop
    at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:765)
    at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:396)
    at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:665)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:523)
    at java.lang.Thread.run(Thread.java:748)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- System Details --
Details:
    Minecraft Version: 1.16.5
    Operating System: Linux (amd64) version 5.4.0-42-generic
    Java Version: 1.8.0_275, Oracle Corporation
    Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 1024 MB / 2048 MB (512 MB allocated, 256 MB free)
    JVM Flags: 2 total; -Xmx2048M -Xms1024M
    ...
Loaded mods:
    Mod1: version
    Mod2: version
    ...

 

Back to top