Eclipse Community Forums: Memory Analyzer

Help

Home

Home » Eclipse Projects » Memory Analyzer » Heapdump is too small

Show: Today's Messages :: Show Polls :: Message Navigator

Heapdump is too small [message #652338]

Thu, 03 February 2011 15:51

Frank

Messages: 2
Registered: February 2011

Junior Member

I am running an Active MQ server. 512MB is allocated to the app and the log says that the heap is 466MB. The monitoring tool (Panorama) confirms this. The monitoring tool also says the app is slowly leaking memory (over weeks) and now only reclaims 20% of the heap after a GC.

We did a heapdump and used MAT to analyze it. The heapdump file is only 92MB and MAT says the heap is 72MB. We see no leak.

Where are all the other hundreds of heap MBs going?

Report message to a moderator

Re: Heapdump is too small [message #652579 is a reply to message #652338]

Fri, 04 February 2011 15:35

Krum Tsvetkov

Messages: 164
Registered: July 2009

Senior Member

Hmm...
One possibility is that the GC which usually happens before the heap dump is triggered cleand up the memory.

Other posibility is that MAT decided a lot of objects are garbage, but as you say that the file is 92mb I would rather asume this is not the case.

Not sure that this will help me give you a better answer, but at least to get a better picture - what is the VM you are using (Sun / IBM). In which format is the dump (if this is an IBM VM) - a .phd file or a system dump?

Do you have some output from the VM about the GC activity, and about writing the heap dumps. Usually from sun VMs you'll see something like
Dumping heap to ...
Heap dump file created [<xxxxxx> bytes in <yyyyy> secs]
?

Krum

Report message to a moderator

Previous Topic:	Error creating heap dump
Next Topic:	Stacktraces while parsing heap

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 16:57:45 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter