When rendering to a drive that becomes full during the rendering process, the Nuke script will crash when the drive becomes full, with no prompt to a possible full drive issue.
There are different results that occur over different operating systems when the drive becomes full.
Windows:
Data can still be written to the drive and when attempting to write out new data to a full drive, there is no error that the drive is full.
Note: Any new scripts that are versioned or created when the drive is full, will create 0kb empty files without letting the user know the drive is full when saving.
When re-opening, as expected the script will be empty, this occurs on both local and server drives.
Linux:
Users will receive an error message that the drive is full, although data can still be written to the full drive.
Note: Any new scripts that are versioned or created when the drive is full, will create 0kb empty files without letting the user know the drive is full when saving
When re-opening, as expected the script will be empty, this occurs on both local and server drives.
Mac:
Users will not be able to save new data and receive a 'bad address' error prompt which does not let you save to the full drive.
Customer reported version
nuke.10.0v5
Customer reported platform
centos7
Steps to reproduce
1) Create a drive or partition on any OS and fill with media to create a full drive (or use a currently full drive).
2) Create a new Nuke script on a drive with free room
3) Set the Nuke script to 300 frames
4) Create a Checkerboard node
5) Connect a Write node to the Checkerboard node and set to default .jpg render settings
6) Select the full drive as the render location.
7) Render files to full drive
Result: Nuke will crash
Windows/Linux only
8) Re-open Nuke script
9) Save a new version of this script to the full drive Result: The script will save without a prompt at 0kb's to the full drive
10) Attempt to open 0kb script
Result: The script will open with no contents
Workaround
No workaround currently, our suggestion is to ensure the drive you are working on has ample space for scripts or the scripts are kept on a separate drive
Reproduced by support
This bug has been reproduced in:
Nuke 11.1v3 - Windows 7 - CentOS 6.9 - MacOS 10.13.4
Nuke 11.1v1 - Windows 7
Nuke 11.0v4 - Windows 7
Nuke 11.0v1 - Windows 7
Nuke 10.5v7 - Windows 7
Nuke 10.5v1 - Windows 7
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7
Nuke 8.0v7 - Windows 7
Nuke 8.0v1 - Windows 7
Nuke 7.0v10 - Windows 7 - CentOS 6.9 - MacOS 10.13.4
Earliest version tested
Nuke 7.0v10
- This issue appears to be in all versions of the product
Expected behaviour
When rendering to a drive that becomes full there should be a prompt in Nuke the drive is almost full.
Actual behaviour
When rendering to a drive that becomes full, Nuke will crash without a prompt.