Q100046: Sending crash reports for Nuke/NukeX/NukeStudio/Hiero
This article provides guidance on how to proceed if Nuke/NukeX/NukeStudio exits unexpectedly or crashes.
When Nuke/NukeX/NukeStudio crashes a crash report (Issue Reporter) dialogue window should appear.
Please fill out the description field with as much information as possible regarding what you were doing at the time of the crash and a unique identifier like name, company or email (this will help us to find crash reports specific to you).
Crash reports only provide certain information, such as the call stack, so it is useful to have context for the actions taken prior to the crash.
Once you click 'Send' and the crash report and information are uploaded to our server you should see the successful upload message:
Crash reports do not go to Support. They go direct to our developers for analysis, to help find common patterns in crashes. As such, you will not receive any response when submitting a crash report.
Please note that in most cases a crash report can not offer enough information to identify the exact cause of the crash.
If you are seeing the crash consistently then we recommend that you contact Support for further investigation and to ensure a bug gets logged in our system.
For this you will need to raise a Support ticket and provide us with the crash report reference number (for the above example 'Reference: c64fe7d4-f2eb-4600-8829-5fb210cd626d' ) together with an example project reproducing the crash and a full list of reproduction steps (or if possible a screen recording).
Nuke/NukeX/NukeStudio can crash for a variety of reasons and while we cannot guarantee that these suggestions will prevent the crash, we would recommend that you try the steps in the following article to begin diagnosing the crash on your end:
NOTE: Sending us an operating system crash log (such as macOS terminal output) will unfortunately not help us identify a possible cause for the crash. This is because the Foundry crash report will provide us with information on the Product level as opposed to just purely at the operating system level.
We're sorry to hear thatPlease tell us why