I'm encountering a slowdown after few days of sleep cycle, and I find I need to restart explorer.exe manually from process explorer. Slowdown is mostly visible when changing virtual desktops, as changing them becomes sluggish.
It appears that there is a private bytes memory leak in explorer.exe (see attachment), it balloons noticably when the slowdown occurs.
- I have also verified that it's not my own in-memory patch to explorer.exe, since the problem in explorer.exe appears without it.
- I also have own DLL that interacts with hidden Virtual Desktop API's in the explorer.exe which could be the problem, not sure why the memory leak would appear in explorer.exe only.
- I've tried to look the list of explorer shell extensions (attachment autoruns.pngf), I couldn't find anything suspect in there, except skype2c, which I have disabled.
I'd like to know what is a good way to debug private bytes memory leak in explorer.exe itself?
I have tried to read up on this "Using UMDH to Find a User-Mode Memory Leak" (MSDN), if there is some tricks to debug memory leak like this, I'd like to know.