Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

memory analyzer leak test print out (help)

 
jim mcnamara
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi-

i am using eclipse memory analyzer leak report print out. i dont think i did anything to cause these.
my coding is just db, application, and gui kind of basic coding. i used simon tuffs one jar and found
it had a leak so i decided to get rid of it. there was a big improvement. but now i have these few.
i am using fatjar eclipse plug-in. i use embedded apache derby, hibernate, fat-jar, swt and some eclipse files in my project.
in linux after opening launching my fatjar application and fooling around i am at about 113 mb of ram.

thanks for any input. well while i am waiting for a possible response i am going to fool around a bit more
with memory analyzer. thanks !

here is the print out:

the class "java.lang.ref.Finalizer", loaded by "<system class loader>", occupies 4,895,648 bytes. The memory
is accumulated in one instance of "java.lang.ref.Finalizer" loaded by "<system class loader>"

The classloader/component "sun.misc.Launcher$AppClassLoader @0xaab17330" occupies
3,799,520 bytes. The memory is accumulated in one instance of "java.util.HashMap$Entry[]" loaded by
"<system class loader>".

One instance of "sun.net.www.protocol.jar.URL.JarFile" loaded by "<system class loader>" occupies
1,534,784 bytes. The memory is accumulated in one instance of "java.util.HashMap$Entry[]" loaded by
"<system class folder>"


























 
jim mcnamara
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi-

i found more tutorials and am finding all kinds of read outs to analyze.
i have some reading to do. i hope to learn a little of this kind of
soon.

thanks,
3rdshiftcoder
 
jim mcnamara
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi-

please disregard my initial post. i did some reading tonight.
this article is so cool.
http://java.dzone.com/news/how-fix-memory-leaks-java

what i have done is held some references and i can clearly see
with memory analyzer that there are differences between shallow
and retained heap at the moment of that snapshot

jmap -heap:format=b 6069 > tmp.dat2

i read about references and understand how to possibly fix a few things now.

i will start thinking about references more when i read my code.

thanks :-)
3rdshiftcoder

thanks,
3rdshiftcoder
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic