If the example application is running on a small memory machine, you should make sure you do not keep unnecessary references to large tables or images that are built by the createImage method. The Heap Analysis tool can analyze the same data for you, but requires a binary report file as input. To generate the binary report, close the TableExample3 window. The binary report file TableExample3.hprof is created when the program exits. The Heap Analysis tool starts an HTTP Server that analyzes the binary profile file and displays the results in HTML that you can view with a browser.
Server is ready.
The above output tells you an HTTP server is started on port 7000 by default. The default report view contains a list of all the classes. What youn look for here are instances in the application that have references to objects that have a risk of not being garbage collected. This can sometimes occur in the case of JNI if memory is allocated for an object, the memory is left to the garbage collector to free up, and the garbage collector does not have the information it needs to do it. In this list of references, you are mainly interested in a large number of references to objects or objects of a large size.