Q100274: How to automatically generate and locate Nuke crash reports

  1. The Foundry SANDBOX
  2. Nuke Family
  3. Troubleshooting

SUMMARY

This article explains how you can enable or disable the creation of crash reports when running Nuke, describes the default locations for reports, and provides guidance regarding how this can be customized.


 

MORE INFORMATION

By default, Nuke's crash reporting is enabled in GUI mode and disabled in terminal mode. This means that when launching Nuke operations via terminal commands, like batch rendering or using Nuke's Python interpreter, the crash reporter window won't appear and you won't be able to submit a crash report if Nuke terminates unexpectedly.
 
To enable crash reporting while Nuke is in terminal mode, or to disable crash reporting altogether, the --crashhandling command line flag or NUKE_CRASH_HANDLING environment variable can be used as described in the sections below.
 
Note: If both the NUKE_CRASH_HANDLING environment variable and --crashhandling command line flag are present, the command line flag will take priority.

 

Enabling Crash Reporting for Terminal mode:

To enable crash report generation, the --crashhandling 1 flag can be used when launching Nuke like the following examples:
Windows: "C:\Program Files\Nuke16.0v4\Nuke16.0.exe" --crashhandling 1
macOS:     /Applications/Nuke16.0v4/Nuke16.0v4.app/Contents/MacOS/Nuke16.0 --crashhandling 1
Linux:        /usr/local/Nuke16.0v4/Nuke16.0 --crashhandling 1
 
Alternatively, the NUKE_CRASH_HANDLING environment variable can be set to 1 prior to launching Nuke:
NUKE_CRASH_HANDLING=1

 

Disabling Crash Reporting for Terminal mode and GUI mode:

To completely disable crash report generation, the --crashhandling 0 flag can be used when launching Nuke like the following examples:
Windows: "C:\Program Files\Nuke16.0v4\Nuke16.0.exe" --crashhandling 0
macOS:     /Applications/Nuke16.0v4/Nuke16.0v4.app/Contents/MacOS/Nuke16.0 --crashhandling 0
Linux:        /usr/local/Nuke16.0v4/Nuke16.0 --crashhandling 0
 
Alternatively, the NUKE_CRASH_HANDLING environment variable can be set to 0 before launching Nuke:
NUKE_CRASH_HANDLING=0

 

Note: If you would like to disable the crash reporter window entirely, while still generating crash reports, please refer to the following article:
Q100451: How to disable the Issue Reporter dialog and write out a crash dump file

 

Locating Crash Reports:

By default, crash reports generated for Nuke 14.1v1+ are located in the following directories:

Windows: C:\Users\<username>\Documents\nuke\<version>\sentry-db\reports
macOS:     /Users/<username>/Documents/nuke/<version>/sentry-db/completed
Linux:        /home/<username>/Documents/nuke/<version>/sentry-db/completed
 
Prior to 14.1v1, crash reports would be created in the following directories:
Windows: C:\Users\<username>\AppData\Local\Temp
macOS:     /tmp
Linux:        /tmp
 
To define a different default location for crash reports files, set the FN_CRASH_DUMP_PATH environment variable before launching Nuke:
FN_CRASH_DUMP_PATH=C:\My\Custom\Path
Note: The FN_CRASH_DUMP_PATH environment variable does apply to Nuke 14.1v1 - 14.1v5
 

FURTHER READING

More information on how to set environment variables for Nuke can be found in this article: Q100015: How to set environment variables

Additional details regarding the crash report submission process can be found in the following article: Q100046: Sending crash reports for Nuke/NukeX/Nuke Studio/Hiero

More information on command line operations for Nuke can be found in this learn page: Command Line Operations

For guidance on the available environment variables in Nuke, please see the Nuke Environment Variables section of the documentation.

    We're sorry to hear that

    Please tell us why