How to Test Crash Reporting and Dumps with Commands

Triggering Test Crashes

You can verify that Crash Assistant Mod is working properly or capture diagnostic files on demand using the /crash_assistant crash in-game command. It accepts three primary targets:

• /crash_assistant crash game: Forces a standard Minecraft crash and creates a standard crash report file to preview the crash screen.
• /crash_assistant crash jvm: Crashes the Java Virtual Machine directly to produce an hs_err_pid diagnostic file.
• /crash_assistant crash no_crash: Executes diagnostic arguments without actually terminating or crashing your Minecraft session.

Appending Diagnostic Dump Arguments

You can attach optional parameters to the command to capture in-depth memory and thread diagnostics:

• --withThreadDump: Generates and embeds an active thread dump directly into your log file.
• --withHeapDump: Produces a complete Java heap dump file on your system.
• --GCBeforeHeapDump: Commands the Java Virtual Machine to run its garbage collector immediately before generating the heap dump, clearing unused memory so only active data is recorded.

For example, running /crash_assistant crash no_crash --withHeapDump --GCBeforeHeapDump gathers memory diagnostics without crashing your current world.