I recommend the only things you make static be strings, and that for everything else you are considering making static, instead write it to file and use static methods, that expect to be passed a context, to access the data.
I think my problems might be camera related, so my plan is to stop using our own camera related activites and just use an intent to launch the camera, and then read the returned result. On Dec 10, 1:05 pm, fadden <fad...@android.com> wrote: > On Dec 8, 12:28 pm, skominac <stevan.komi...@gmail.com> wrote: > > > So not only is memory of static members not deallocated (which is > > actually not surprising), but the static references are still alive, > > pointing to the memory, and can be used to invoke the members back. > > This last part was surprising to me. > > > This is actually not bad, as long as developers are aware of it. > > Is this Dalvik's feature? > > This is the expected behavior. Keep in mind that the VM doesn't shut > down between runs of your activity. You are not necessarily starting > with a clean slate. -- 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
