I have activity "A" that launches phones Image Gallery for the user to
pick a picture. In some cases the OS decides there is not enough
memory and kills my process.
In A's onActivityResult() I start a thread that does some lengthy work
with the picture. This thread depends on A.blah field, that is set in
onCreate() (or should be).
According to this http://developer.android.com/guide/topics/fundamentals.html#actlife
when my process is killed the onCreate() is called and so A.blah
should be initialized and so my threads run() method that is invoked
from onActivityResult() should not get null reference, but it does.
Is there any way for me to debug this? I mean can I somehow force the
phone or emulator into killing my process so I can put the breakpoints
and see what's going on?
I can't reproduce it on my phone but my customers are experiencing the
problem.
Thank you!
--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment