Thanks - I read that post; it seems to be stuck in the same place I am. I suspect a memory leak that is keeping some app state alive across app shutdown and restart, and what I'd really like is some easy way to analyze what memory isn't being reclaimed when Android closes my app.
On Sunday, November 11, 2012 9:18:37 PM UTC-5, Nikolay Elenkov wrote: > > On Mon, Nov 12, 2012 at 7:17 AM, Nobu Games > <dev.nob...@gmail.com<javascript:>> > wrote: > > Post your manifest.xml. I assume that you have your broadcastreceiver or > > some service running in a separate process. That would cause > > Application.onCreate to be called multiple times. > > > > ACRA keeps track of initialization using a static variable, so with > multiple processes > this should not happen. I've seen this too in error reports, still no > idea why it happens. > Here's a related issue: > > https://github.com/ACRA/acra/issues/3 > -- 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
