ansaurus

Question

Does Android kill local variables after some time?

Answer 1

A:

The error speaks by itself: NullPointerException. Just try to see why are you getting a null value there, and try to catch it also...

 catch (JSONException e) {
            System.out.println(e);
 }
 catch (NullPointerException n) {
            // do something useful here
 }

Cristian 2010-09-08 05:05:11

I can prevent the crash by catching the nullpointerexception, but from the answer above, it looks like the OS is killing my process and skipping onCreate(). How can I handle this properly?

Sheehan Alam 2010-09-08 06:31:24

It doesn't skip onCreate() if it kills the process. It *has* to do onCreate() to display the current activity after that, because it will need to create the activity. It just may create activities in a different order than originally, because they are only created as they are shown. You just need to deal with this. (And to the original comment -- just catching NullPointerException is at best a band-aid if not outright wrong; the code just needs to deal correctly with things so this doesn't happen.)

hackbod 2010-09-08 06:37:53

is it hacky to check for null in onStart() or onResume() and re-initialize there?

Sheehan Alam 2010-09-08 15:33:32

Not at all... in fact that's what you have to do :D

Cristian 2010-09-08 15:52:22

Answer 2

+1 A:

I experienced similar problems earlier. It is not that Android kills some variable, but because after some time Android kills the process, when you start the program again, the program is started not on the first activity, but the last activity you were on. Therefore you may get some variables that you usually have them initialized on the first activity not initialized.

yuku 2010-09-08 05:15:03

how did you resolve this?

Sheehan Alam 2010-09-08 05:58:01

Initialize the variables on the onCreate of each activity, not only the main activity.

yuku 2010-09-08 06:59:03

ansaurus

tags:

views:

answers:

Does Android kill local variables after some time?

related questions