ID 272435 - Custom DiskCachePath causes hang on launch and memory leak

Problem summary
Setting the DiskCachePath in Nuke preference will cause Nuke to stall on launch and suck up all the system memory. 

Customer reported version
Nuke10.5v3

Customer reported platform
windows10

Steps to reproduce

1) Clear your .nuke directory and create an empty C:/temp/ directory

2) Download the attached preferences files and add them to the .nuke directory and make sure 

3) Launch Nuke 10.5v4 in verbose mode on Windows, it will hang at "Loading C:/Program Files/Nuke10.5v2/plugins/getenv.tcl", and just fill the RAM.

Workaround

Option A
1) Open up a new window to the 'C:/temp/' directory, or the current directory your Nuke cache location is set to
2) Create a new directory in here called 'tileCache'
Result: When you reload Nuke it will function correctly

OR

Option B
1) Open up the .nuke directory. Information about finding your .nuke directory can be found here: Q100048: Nuke Directory Locations
2) Open the preferences.nk file in Notepad or a text editor
3) Change the DiskCachePath to 'C:/temp' rather than 'C:/temp/'
4) Save file
Result: When you reload Nuke it will function correctly
 

Reproduced by support
This problem has been reproduced on:

Nuke 10.5v4 - Windows 10

Nuke 10.5v2 - Windows 10 

Nuke 10.5v1 - Windows 10 

This problem was not reproduced on:

Nuke 10.5v4 - MacOSX 10.12 - CentOS 6.8

Nuke 10.5v1 - MacOSX 10.12 - CentOS 6.8

Nuke 10.0v6 - Windows 10 - MacOSX 10.12 - CentOS 6.8

Nuke 10.0v1 - Windows 10

Expected behaviour
For Nuke to load correctly 

Actual behaviour
It hangs and fills the RAM after loading plugins/getenv.tcl