ID 199721 - Repeatidly saving a file via the hotkeys can cause memory leaks in Nuke Studio

Follow

Problem summary
Spamming the save process in Nuke Studio will increase the process memory dramatically. Doing so you can reach 1 GB starting from 230 MB (the initial memory) in about 1 minute.
The memory is in average increased with 1 MB for each save.

Customer reported version
nuke.11.0v1

Customer reported platform
centos6

Steps to reproduce

  1. Open Nuke Studio
  2. Import the attached XML
  3. Save the project to any valid path
  4. Open Task Manager
  5. Rapidly save the script by pressing ctrl + s in a constant motion (Button Mash)
  6. Observe how to memory is increased

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