ID 133125 - Command line option for memory (cache) -c option specifies bytes can be used but bytes value is not respected

Problem summary
When running Nuke, NukeX, NukeStudio or Hiero in Command Prompt with a limited memory cache size prompt ( -c "cache size" ), If the user decides to use Bytes, it is not calculated correctly.

For example:
If a user decides to use a 10GB cache size, but inputs it in as Bytes to the Command prompt ( 10737418240b )  they will receive half the Maximum cache size: ( 4294967295b )
 

Steps to reproduce

(Windows Reproduction: )

1)  Open your start menu type in 'cmd', open the file

2)  Middle-click drag and drop your Nuke executable into the cmd, add the following: ( -c 10737418240 )

     Example:

"C:\Program Files\Nuke11.0v3\Nuke11.0.exe" -c 10737418240

3) Once Nuke is open, enter your Script Editor 

4)  Enter the following script and execute it:

print 'Nukes max usage: ',nuke.memory('max_usage')print 'Expected max usage: 10737418240'

Result: Nuke's max usage will be 4294967295 Bytes which is under half the expected amount.

Workaround
Specify the memory cache with an expected variable as described in our Online help Documentation: "k (kilobytes), M (megabytes), or G (gigabytes) after size."
Command-Line operations - Nuke Online Help

For example:

"C:\Program Files\Nuke11.0v3\Nuke11.0.exe" -c 10G

Reproduced by support

This bug has been reproduced in:
Nuke11.0v2 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v1 - Windows 7
Nuke10.5v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v1 - Windows 7
Nuke10.0v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v1 - Windows 7
Nuke9.0v9 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v1 - Windows 7
Nuke8.0v7 - Windows 7 - Mac10.12 - CentOS6.9
Nuke7.0v10 - Windows 7 - Mac10.12 - CentOS6.9

Earliest version tested
- This issue appears to be in all versions of the product

Expected behaviour
Nuke's max usage should be the amount of Bytes inputted by the user.

Actual behaviour
Nuke cannot calculate the heavy amount of Bytes given.