Re:New (revolutionary?) solution for Java memory leak discov...
by yxhuvud on Tuesday January 24, 2012 @06:31AM
(#3504302)
Finding out that you have a memory leak is a lot easier than to find what part of the code is responsible for that leak, for nontrivial code sizes.
[ Parent
| on HN ]
There are no comments on this comment yet.