Not fixed in Process Explorer 16.30 (new in the last 60 days) – John – 2019-11-21T01:44:05.297
I don't think the problem is with ProcessExplorer itself, I see the same thing using PowerShell's Get-Process command. I don't know how normal it is, found this thread looking for an answer on tracking processes using "Committed memory" since mind get in the 60GB range over a day without reboot. – Simon Berthiaume – 2019-12-07T14:38:42.703
Answers
0
I think I found the answer on StackOverflow: it seems this is expected when applications are built to support what is called Control Flow Guard (CFG).
I see the same thing in Process Explorer V16.26 64-bit here on my Windows 10 machine. There is an explanation here: https://stackoverflow.com/questions/3030274/what-is-virtual-size-in-sysinternals-process-explorer . I do not use the column and otherwise nothing is wrong here
– John – 2019-11-21T01:33:35.283Not fixed in Process Explorer 16.30 (new in the last 60 days) – John – 2019-11-21T01:44:05.297
I don't think the problem is with ProcessExplorer itself, I see the same thing using PowerShell's Get-Process command. I don't know how normal it is, found this thread looking for an answer on tracking processes using "Committed memory" since mind get in the 60GB range over a day without reboot. – Simon Berthiaume – 2019-12-07T14:38:42.703