ID 147437 - RAM usage increases uncontrollably when playing cached frames

Problem summary
Nuke is taking up to 100% of available RAM although the comp cache size has been set to 50%
After changing a parameter and playing back the footage a second time, Nuke uses a lot more RAM than the first time and will take up 100% of available RAM.

Clearing all caches does not bring down the RAM usage sufficiently.
Only deleting the nodes, or closing the comp, clears the RAM.

Customer reported version
nuke.11.1v1

Customer reported platform
windows10

Steps to reproduce

1) Open Nuke.

2) Ensure that the cache is cleared (Cache > Clear All)

3) In Project Settings (Edit > Project Settings) change the frame range to 1-200.

4) Copy and paste the following code into the node graph.

set cut_paste_input [stack 0]
version 11.1 v1
push $cut_paste_input
Noise {
 zoffset {{frame}}
 center {1024 778}
 name Noise1
 selected true
 xpos -414
 ypos -134
}
Kronos {
 retimedChannels all
 timingOutputSpeed 1
 showLegacyMode false
 motionEstimation Regularized
 Shutter 1
 shutterSamples 5
 shutterTime 0.5
 legacyModeNuke9 false
 name Kronos1
 selected true
 xpos -414
 ypos -48
}
Transform {
 skewX 0.1
 center {1024 778}
 name Transform1
 selected true
 xpos -414
 ypos 34
}
Viewer {
 frame_range 1-200
 full_frame_processing true
 name Viewer1
 selected true
 xpos -330
 ypos 119
}

5) Navigate to the Preferences dialog (Edit > Preferences... > Performance/Caching) and ensure the comp cache size (%) is set to 50, and click OK.

6) Play the comp all the way through and open Task Manager (Ctrl + Shift + Esc). Under the performance tab, notice how the Memory usage is increasing.

7) Change one of the values on the Transform node (for example set the skew to -0.1).

8) Play the footage through and open the Task Manager again.

9) Notice that the Memory usage will keep increasing until 100%

Workaround
Unknown.

Reproduced by support

This bug has been reproduced in:
Nuke 11.1v1 - Windows 10 - Linux CentOS 6 

Nuke 11.0v4 - Windows 10 

Nuke 11.0v1 - Windows 10

Nuke 10.5v7 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v6 - Windows 10

Nuke 9.0v9 - Windows 10 

Nuke 9.0v1 - Windows 10 - Linux CentOS 6 - Regression

Unable to reproduce bug in:

Nuke 11.1v1 - Mac OSX El Capitan

Nuke 9.0v1 - Mac OSX El Capitan
Nuke 8.0v7 - Windows 10 - Linux CentOS 6

Was unable to reproduce on Mac OSX El Capitan

Earliest version tested

Nuke 8.0v7 - Windows 10 - Linux CentOS 6

- This issue no longer appears in this version and has regressed

Expected behaviour
Nuke should only use the amount of Memory specified in the Preferences.

Actual behaviour
After changing a parameter and playing back the footage a second time, Nuke uses a lot more RAM than the first time and will take up 100% of available RAM.