Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am analyzing a heap dump using a jvisualvm. From the report I can see the classes, number of instances and the size occipied.
What I wanted to know is – the source (which class instantiated) of these objects. For a given object, if I could know all the source classes and the number of instances created by each of those classes, I guess it would be easy to identify the bad candidate.
Is this possible at all? If so, is there any tool better than the other to provide such information?
YourKit provides allocation tracing by size and by number. You can search for particular classes created and find hot spots. The evaluation version is free. 😉