This article provides guidance on how to proceed if Nuke/NukeX/Nuke Studio/Hiero exits unexpectedly or crashes.
When Nuke/NukeX/Nuke Studio/Hiero crashes, a crash report (Issue Reporter) dialogue window should appear:
Please fill out the Feedback field with as much information as possible regarding what you were doing at the time of the crash. Then, please fill the Name and Email fields with your information, as this will help us locate 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 Report", the crash report information is uploaded to our server and you should see the successful upload message at the bottom of the window:
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 experiencing a crash consistently, then we recommend you contact Support for further investigation and to ensure a bug is logged in our system.
For this, you will need to raise a Support ticket and provide us with the crash report reference ID number (for the above example ID: 7f6c871f-ebd7-41d9-a844-fa11b8077f38 ) together with an example project reproducing the crash and a full list of reproduction steps (or a screen recording if possible).
Nuke/NukeX/Nuke Studio/Hiero 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