Crash Reporter Explained

CrashReporterBreakdown.png

There have been quite a few questions about the overall workflow regarding the Crash Reporter. This tool helps to provide specific information to Epic about particular crashes, which in turn assists us in reproducing bugs so that we can get them fixed. Here is a general breakdown of how this feature works:

  1. Project Name - This is the project you were working in when the editor crashed
  2. Description - This is one of the most important aspects of the crash reporter. When submitting, please provide the steps you were taking prior to the editor crashing. The more detailed the description, the better we can follow your instructions to attempt to reproduce this on our end, which leads to faster bug reporting.
  3. Callstack - This callstack gives some information aobut what occurred to cause the crash
  4. Copy Callstack to Clipboard - Creates a copy of the callstack if you need to paste it to a new location.
  5. Submit/Don't Send - Pressing submit sends the callstack and relevant information you provided in the description to Epic's Crash Reporter so we can attempt to reproduce this on our end. This is recommended as any information you can provide that helps us to reproduce an error leads to faster bug reporting. You can, however, opt to press Don't Send, which will not send any information to Epic.