Jprofile viewing hprof files [go]

Open the Hprof file with Jprofile to see the memory leaks, there are a few common features to illustrate:
Tool Download: Download jprofile7.0.1 64-bit to the official website. Re-apply for a registration number, the registration number of the application seems to be an email can only be used once.
1. Open the Hprof file: Enter the classes view, based on (instance count and size) basic can determine which class of the object has problems. For example (there are 2,731,062 instances of the Java.util.linkedlist$entry Class).
2, according to common sense, should be Java.util.LinkedList class has an object size should be very large.
3. View Java.util.LinkedList, right-->use Selected Instance
4. Select Outgoing reference view (you can view other object handles owned by the object, that is, object properties). Look at the retained size column (or the Size property) (sometimes retained size doesn't work), and the size will determine which object is out of memory.
5, find the corresponding object, right-click->use Selected Instance
6. Select Incoming refrences view (this view shows which objects have a handle to this object), in this view there is a show Paths to GC root button, click, Basic can determine which code we have a problem.

Jprofile viewing hprof files [go]