ID 539682 - GUI path processing still happens in terminal mode, using more RAM than necessary

Problem summary
GUI path processing still happens in terminal mode, using more RAM than necessary
 
The attached test_RAM_scene_suspend.nk runs nuke.suspendPathProcessing() on startup, whereas test_RAM_scene_nosuspend.nk doesn't, which in Terminal mode, should not make a difference to the amount of Ram used by Nuke
 
Customer reported version
nuke.12.2v5
 
Customer reported platform
centos7
 
Steps to reproduce
 
1) Download the attached test_RAM_scene_nosuspend.nk or test_RAM_scene_suspend.nk Nuke scripts

2) Open a system resource monitor like OpenHardwareMonitor or btop to monitor RAM usage over time

3) Open a terminal and run the following command, and notice the RAM usage:
 

<Path/to/Nuke/install> --safe -F 1 -x <path/to>/test_RAM_scene_nosuspend.nk

 
 
4) Open a terminal and run the following command, and notice the RAM usage:
 

<Path/to/Nuke/install> --safe -F 1 -x <path/to>/test_RAM_scene_suspend.nk

 
btop on CentOS 7.9:

OpenHardwareMonitor on Windows 10:

 
Expected behaviour
For the amount of RAM used by Nuke for rendering to be consistent in terminal mode
 
Actual behaviour
When using nuke.suspendPathProcessing(), this decreases the amount of RAM used by Nuke in terminal mode.
 
Workaround
Use nuke.suspendPathProcessing() to decrease the amount of RAM Nuke uses
 
Reproduced by support
This bug has been reproduced in:
Nuke 14.0v4 - Windows 10, CentOS 7.9, macOS Monterrey
Nuke 10.0v1 - Windows 10, CentOS 7.9
 
Earliest version tested
Nuke 10.0v1 - This issue appears to be in all tested versions of the product