heapSpank only displays the top 10 candidates for memory leaks, and an algorithm chooses which 10 to display.
As good stewards of the heap, we are often interested in memory consumption of other classes, like ones that
do not leak, but take up ginormous portions of your heap, like cached data
have caused memory problems before
are suspect or of concern for some other reason
To address these needs, heapSpeak must let the user specify 'special' class names in a configuration file that heapSpank will always display, in addition to the regular 'top 10'.
heapSpank only displays the top 10 candidates for memory leaks, and an algorithm chooses which 10 to display. As good stewards of the heap, we are often interested in memory consumption of other classes, like ones that
To address these needs, heapSpeak must let the user specify 'special' class names in a configuration file that heapSpank will always display, in addition to the regular 'top 10'.