Memory service reporting 2TB of used Virtual Memory

Last Modified

Thu Oct 04 16:01 GMT 2018

Description

  • This article provides brief information on seeing virtual memory using an unrealistic amount of memory in the Memory service.

Environment

  • N-able N-central version 10.x or later

Solution

  • This is not an N-able N-central or Agent problem, but a windows issue. The problem in these situation is that windows is actually returning this value, and all we can do is report on this.

If we check the performance counter for the process to see what the virtual bytes do come back as 2TB.

Command: typeperf -sc 5 "\Process(explorer)\Virtual Bytes"

If you want to check a different process just change what is in the ().

Output:
"(PDH-CSV 4.0)","\\MBC***\Process(explorer)\Virtual Bytes"
"05/09/2016 16:02:05.797","2199529127936.000000"
"05/09/2016 16:02:06.813","2199529127936.000000"
"05/09/2016 16:02:07.829","2199529127936.000000"
"05/09/2016 16:02:08.829","2199529127936.000000"
"05/09/2016 16:02:09.844","2199529127936.000000"
Exiting, please wait...
The command completed successfully.

2199529127936 bytes = 2.199529127936 terabytes

You might not want to go through the process below because it is a bit intensive, but there is the command lodctr /r. It does a basic performance counter reload so may or may not help.