To set the stage: I'm wrestling with OutOfMemoryExceptions, and beginning to suspect heap fragmentation as the root cause.
I know that the hprof files dumped from the monitor tool are a slightly different format (JAVA PROFILE 1.0.3) from the "standard" java hprofs (JAVA PROFILE 1.0.2). I know that hprof-conv can convert a 1.0.3 formatted hprof to a 1.0.2 formatted hprof. I also think I've found a spec for the binary 1.0.2 format [1]. However, I was curious about the 1.0.3 format and have just done some searching, but haven't been able to find anything describing it on the developers.android.com site or the AOSP site at source.android.com. Is the 1.0.3 format documented and described anywhere? I have looked at both YourKit and MAT to analyze the heap dumps, but neither of them address fragmentation at all. I guess fragmentation is not much of an issue for server and desktop jvms. The hprof format appears to contain address information, so some kind of fragmentation analysis should be possible. I read that ART's GC will also eventually be a compacting collector, which is good news! In the meantime I'd like to try to use the address information in the hprof files to estimate heap fragmentation. Dave -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
