Analysing a JVisualVM profile - finding the source of large numbers of primitive types?
- by MalcomTucker
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