compiled with java 1.6

Same as v0.8 but compile with Java 1.6

Config file support with bug fixes.

heapSpank now has its own config file -- heapSpank.properties.
You can tweak parameters in this file to slow down or speed up the frequency that jmap -histo is called.
To keep low overhead, by default, the jmap -histo -live option is not used -- it forces lots of extra GC cycles.
But, you can change this too, in the config file if necessary.

See the main page for details:

https://github.com/eostermueller/heapSpank

Details on all changes: #3, #9, #14.

jmap no longer has to be in your path!

• heapSpank no longer requires jmap to be in your path! Instead, tools.jar from your JDK is used to capture jmap -histo data.
• pid is now displayed on heapSpank display.
• support for -selfTest option for troubleshooting tools.jar location issues.
• MD5 for this jar: c9c9220ba3d766cd02a6b64fb2f6e18c

-jar support and custom configuration

• Launch heapSpank using -jar syntax:
  java -jar heapSpank-0.6.jar 8173
• No support yet for a configuration file, so all config changes must be done via code. Just create a new class to extend DefaultConfig as shown here and pass in your subclass name with the -config parameter, like this:
  java -jar heapSpank-0.6.jar 8173 -config com.github.eostermueller.heapspank.leakyspank.console.FifteenSecondJMapHistoInterval

leakySpank Console support!

This release allows you to detect memory leaks on a JVM running on a headless machine.
Only MacOS and linux have been tested.

First Release

Detect Java Memory leaks with this tool that captures and analyzes instance and byte counts from JAVA_HOME/bin/jmap -histo