Re: [android-developers] Tracking down multiple Activity instances in memory
On Wednesday, September 10, 2014 6:02:58 AM UTC-7, TreKing wrote: On Tue, Sep 9, 2014 at 11:00 PM, Nathan nathan@gmail.com javascript: wrote: Any tips on finding the causes better? Review your Activity class implementation and look for any place where you save a static variable I have. It's not giving itself up that easily. I was hopeful, in the vast array of information in Memory Analyzer, that something, somewhere, would be useful in narrowing it down. But, so far, all leads have been useless. I have review all 347 or so outgoing references to the context. I'm finding nothing that should last longer than the activity pointing back to the activity. (like a cached Bitmap) using the Activity as a Context. That's the usual culprit. The Android.Graphics.Bitmap class, to my knowledge, does not have any context reference. It is code that has had multiple people working in it and uses some external libraries. So the problem could be deeper, I just wish there were more clues. Nathan -- 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.
Re: [android-developers] Tracking down multiple Activity instances in memory
On Mon, Sep 15, 2014 at 4:14 PM, Nathan nathan.d.mel...@gmail.com wrote: (like a cached Bitmap) using the Activity as a Context. That's the usual culprit. The Android.Graphics.Bitmap class, to my knowledge, does not have any context reference. Yeah, sorry, was thinking of drawables, specifically BitmapDrawable. The only thing I could suggest would be a strategy of stripping down your code to as much as possible and then re-adding stuff back in slowly to see what introduces the issue. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- 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.
Re: [android-developers] Tracking down multiple Activity instances in memory
On Tue, Sep 9, 2014 at 11:00 PM, Nathan nathan.d.mel...@gmail.com wrote: Any tips on finding the causes better? Review your Activity class implementation and look for any place where you save a static variable (like a cached Bitmap) using the Activity as a Context. That's the usual culprit. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- 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.
