On windows 10 one of our users is getting a virtual memory error. Upon investigation, svchost is using 24 gigs of memory. When I do a memory dump and run a memory analysis using windows debugging tools, it shows that none of the treads or loaded modules are using more than a few hundred megabytes. The total of all of the memory all threads are using is about a gigabyte, yet it has 24 gigabytes of committed memory.
What could possibly be using this?
If I stop each service one by one, no individual service frees the gigabytes of memory used, but if I kill the svchost process, it respawns itself and starts back at a reasonable 200 MB. It takes about a week of the PC being on for memory usage to get this high.
No comments:
Post a Comment