Kirk Pepperdine wrote an interesting article about his experience with Netbeans profiler and heap walker. I like the following quote.
What Gregg and I found when we did this [display the shortest path between the leak and the GC root] was not only the source of the leak but we made a more interesting observation. The source of the leak was the only domain object between the GC root and the object that was leaking.
Personally, I hope that tooling of this sort can eliminate all the reference leaks
from the libraries we all use. For instance, JDBC drivers are notorious for reference leaks. Man could I have used something like that back in the day…
Tags: Java, Java Heap Walking, Netbeans, Profiling
Post a Comment