Memory leak in VMOverviewView

[GoogleCodeExporter]

Memory leak in VMOverviewView

[GoogleCodeExporter]

Thanks, I know what you mean - but I would not call it a leak. 

Jvmtop needs the information which PID/JVMs have been requested before in order 
to not need to request them within every refresh interval as this would 
increase cpu usage significantly.

Please note that terminated processes are not the only reason why jvmtop cannot 
connect to them. Security-related reasons are very common, too.
Your patch would fix the memory leak but with the cost that jvmtop would try to 
connect to all others processes which are still alive but could not be 
connected for some reason within every refresh interval.

Additionally, the memory increment is minor for most users/use case scenarios 
so I did a trade-off between memory and cpu usage.

However, I agree that the current solution isn't perfect - jvmtop should remove 
all Map entries for processes which have really been terminated - but keep all 
others.

Original comment by [email protected] on 18 Aug 2014 at 3:47