Okay, starting to debug this by printing out Runtime() memory stats around setContentView(). There is less memory available than ddms says (500K vs 1.5 MB). So maybe it is really running out.
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? -- Ward >All of sudden I am seeing oddball OMM errors when inflating view trees. > >The allocations are from really small (couple of K) to fairly large >(couple of hundered K). > >But ddms says the heap is only half full and there's around 2MB >available. The app does not appear to be leaking. > >What should I be checking? > >Thanks all, > >-- Ward > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
