Analysing a JVisualVM profile - finding the source of large numbers of primitive types?

Posted by MalcomTucker on Stack Overflow See other posts from Stack Overflow or by MalcomTucker
Published on 2010-03-13T10:53:15Z Indexed on 2010/03/13 11:05 UTC
Read the original article Hit count: 286

Filed under:
|

I am trying to reduce the memory footprint of my application. JVisualVM heap dumps report that the objects taking up the most space are:

  • char[]
  • byte[]
  • int[]

Which isn't particularly helpful. How can I track these objects back to the parent classes that are holding them?

Thanks

© Stack Overflow or respective owner

Related posts about java

Related posts about profiling