I got a dump and jhat working -- thanks for the tip fadden. But I still don't see any monster allocations or leaks. This trace just came in:
04-07 10:06:56.341 D/ActivityBase( 820): setContentView(v) aft memory: T:5767 - F:1167 (KB) ...(do some work, but certainly don't do any any monster allocations) ... 04-07 10:06:59.101 E/dalvikvm-heap( 820): 26840-byte external allocation too large for this process. 04-07 10:06:59.101 E/ ( 820): VM won't let us allocate 26840 bytes 04-07 10:06:59.161 D/AndroidRuntime( 820): Shutting down VM 04-07 10:06:59.161 W/dalvikvm( 820): threadid=3: thread exitin According to System.freeMemory I have 1.1 MB of heap right after setContentView(), and yet I can't allocate a lousy 26K 4 seconds later. Puzzling. >On Apr 3, 2:22 pm, Ward Willats <[email protected]> wrote: >> Are there any tools besides ddms to look at the heap? My app is using >> over 2 MB just sitting there -- and the ddms "track allocations" >> don't add up to near that amount. How can I get a good picture of >> what is going on in heapville? > >If you're on the emulator (or have root access on your device), you >can create a heap dump. Some info here: > > >http://groups.google.com/group/android-developers/browse_thread/thread/2597bcce2dffd921 > >In "cupcake" you can dump it with android.os.Debug.dumpHprofData >(String filename). > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
