Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Memory Analyzer » Help in analysis (Memory analysis.)
Help in analysis [message #1035069] Sat, 06 April 2013 05:10 Go to next message
ss ss is currently offline ss ss
Messages: 7
Registered: April 2013
Junior Member
Dear All,
I am new to this Memory Analyser tool. I am running a socket based application run the a database pooling and will various select and insert statements in it. Below is my results from the leak hunter.Suspect 2 I guess is due to nature I am pooling so the connection are alive all the time. I cant intepret well the suspect 1 as when I press the details it give a long list of following details.


java.lang.ref.Finalizer @ 0xf5e19670 40 92,688 
next java.lang.ref.Finalizer @ 0xf5e1a6a8 40 93,024 
next java.lang.ref.Finalizer @ 0xf5e1bda0 40 122,768 


Suspect 1.

The class "java.lang.ref.Finalizer", loaded by "<system class loader>", occupies 1,337,176 (30.93%) bytes. The memory is accumulated in one instance of "java.lang.ref.Finalizer" loaded by "<system class loader>".

Keywords
java.lang.ref.Finalizer


Suspect 2
 6 instances of "com.mysql.jdbc.JDBC4Connection", loaded by "sun.misc.Launcher$ExtClassLoader @ 0xf58bf000" occupy 432,624 (10.01%) bytes. 

Biggest instances:

•com.mysql.jdbc.JDBC4Connection @ 0xf61c54f8 - 94,864 (2.19%) bytes. 
•com.mysql.jdbc.JDBC4Connection @ 0xf61c4678 - 86,600 (2.00%) bytes. 
•com.mysql.jdbc.JDBC4Connection @ 0xf61c4bf8 - 85,456 (1.98%) bytes. 
•com.mysql.jdbc.JDBC4Connection @ 0xf626c348 - 68,000 (1.57%) bytes. 
•com.mysql.jdbc.JDBC4Connection @ 0xf626c7d0 - 68,000 (1.57%) bytes. 


Keywords
com.mysql.jdbc.JDBC4Connection
sun.misc.Launcher$ExtClassLoader @ 0xf58bf000


Re: Help in analysis [message #1059013 is a reply to message #1035069] Thu, 16 May 2013 04:32 Go to previous messageGo to next message
Andrew Johnson is currently offline Andrew Johnson
Messages: 118
Registered: July 2009
Senior Member
The Finalizer object just holds details of objects due to be finalized. Run Java Basics > Finalizer Overview to find out more.

Your total heap is only 432,624 / 10.01% = 4221kB, so I don't think you have a memory problem unless you are running your application on really old hardware or a some kind of small scale device rather than a general purpose computer.
Re: Help in analysis [message #1059024 is a reply to message #1035069] Thu, 16 May 2013 05:30 Go to previous message
ss ss is currently offline ss ss
Messages: 7
Registered: April 2013
Junior Member
Dear Andrew,
I have set my initial and maximum heap as 256Mb on a 8Gb machine. So when do you decide based on the heap size that it is a memory issue or problem. What size of the heap is an indicator of problem? Ok I got it about the finalizer is those where in the final statement rite. How about those link to classloader what is that indicates? What are the other feature of memory analyse can be useful to detect any type of problem?
Previous Topic:How to open a HTML report via MAT in Eclipse?
Next Topic:MAT Main Menu Missing
Goto Forum:
  


Current Time: Mon Jul 28 16:43:33 EDT 2014

Powered by FUDForum. Page generated in 0.11209 seconds