State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:199721|
Customer reported version
nuke.11.0v1
Customer reported platform
centos6
Steps to reproduce
Workaround
Instead saving in rapid succession simply save the file once.
Reproduced by support
NukeStudio 11.0v2 - CentOS 6.9 - MacOS 10.13 - Windows 7
NukeStudio 11.0v1 - CentOS 6.9 - MacOS 10.13 - Windows 7
NukeStudio 10.5v6 - CentOS 6.9 - MacOS 10.13 - Windows 7
NukeStudio 10.5v1 - CentOS 6.9 - MacOS 10.13 - Windows 7
NukeStudio 10.0v6 -
NukeStudio 10.0v1 -
NukeStudio 9.0v9 - CentOS 6.9 - MacOS 10.13 - Windows 7
NukeStudio 9.0v1 - CentOS 6.9 - MacOS 10.13 Windows 7
Earliest version tested
Nuke Studio 9.0v1
Expected behaviour
Nuke would save using memory temporarily raising memory as it saves but clearing it after the save.
Actual behaviour
In most cases Nuke would save the files but still save the process in memory so by repeatidly pressing the save hotkey the memory will progressively add onto itself. This was not present in the Nuke 10.0 tested releases.
We're sorry to hear that
Please tell us why