Author: snazy
Subject: ** Process Explorer Bugs **
Posted: 16 July 2014 at 2:02pm
Hi there,
Process Explorer v16.02 has a memory leak.
Upon start of PE, it consumes about 55MB - that's ok.
After a lot of processes have run (started and terminated) memory consumption raised to 120MB and does not decrease. This morning I restarted PE because it consumed >500MB.
It's non a Handle leak (neither handle, GDI handle nor user handle) - they seem to be cleaned up.
It can be reproduced as follows:
* Machine: Intel Core i5, Windows 7 Enterprise
* Run (the same) process a lot of times. For example if a lot of "git" or "svn" processes are ran by an IDE or from a script.
* PE-View is the "tree" view including the columns process, pid, user name, CPU, priv bytes, working set, CPU history, IO history, description, company name, threads
* The leak seems to appear "faster" when these "temporary" processes are immediatly "rendered" in the tree view.
Robert
Subject: ** Process Explorer Bugs **
Posted: 16 July 2014 at 2:02pm
Hi there,
Process Explorer v16.02 has a memory leak.
Upon start of PE, it consumes about 55MB - that's ok.
After a lot of processes have run (started and terminated) memory consumption raised to 120MB and does not decrease. This morning I restarted PE because it consumed >500MB.
It's non a Handle leak (neither handle, GDI handle nor user handle) - they seem to be cleaned up.
It can be reproduced as follows:
* Machine: Intel Core i5, Windows 7 Enterprise
* Run (the same) process a lot of times. For example if a lot of "git" or "svn" processes are ran by an IDE or from a script.
* PE-View is the "tree" view including the columns process, pid, user name, CPU, priv bytes, working set, CPU history, IO history, description, company name, threads
* The leak seems to appear "faster" when these "temporary" processes are immediatly "rendered" in the tree view.
Robert
