Android:why static variable is set to null on Activity onCreate

Question

The code is like below:

public class MyTestHelperHelper {
    static MyTestApi storeApi = null;
    public static synchronized void initial(Application application) {
        if (storeApi == null) {
        storeApi = new MyTestApiImplImpl();
        storeApi.initiImplal(application);
       }
    }
    public static MyTestApi getInstance() {
        return storeApi;
    }
}

MyTestHelperHelper's initial method is called in Application's onCreate, which is in UI thread. MyTestHelperHelper's getInstance method is called in the Activity's onCreate, which is also in UI thread.

In most case, it works normally. But sometimes, it return null with MyTestHelperHelper's getInstance, which leads to the NPE when I do further operations.

Though the case is rare, I can see it several times in the crash report. I just don't quite understand why:

There is no write to the "storeApi", except in the initial method.
Both initial and getInstance is in main thread, because initial is called in Application onCreate, and getInstance is called in Activity onCreate.
If my app is in background and process is killed, I think the application will be re-created when bring to foreground, so the initial is called.

Seems the NPE occurs only when

1.process starts without application's oncreate. OR

2.When memory is low, many process data, including static variables, classloaders, classes, etc, are cleaned, except the application instance stays in the process. Is it possible?

initial is called on Application onCreate, and getInstance is called onActivity onCreate, both are synchronous. — mianlaoshu
– mianlaoshu, Commented Apr 10, 2018 at 6:19

Sagar · Accepted Answer · 2018-04-10 06:40:17Z

2

It is not possible that a process is newly created and Application.onCreate() is not called.

Whenever a process is created, Application.onCreate() will be called.

However there are certain scenarios where lifetime of static variables could be impacted.

Lifecycle of static variable starts with class been loaded by the JVM and ends with class being unloaded.

A static variable will remain alive as long as one of following won't happen:

The class is unloaded due to low memory conditions.

Note: In this case Application object still persists since it will be the last object to be deallocated. This deallocation cannot be controlled by apps but determined by OS. This could happen if your app is in background and OS wants to relinquish the memory.
The process is killed -> Both static object and Application object are deallocated.

You can use onSaveInstanceState() and onRestoreInstanceState() to save and restore state of your static variable respectively.

edited Apr 10, 2018 at 6:40

answered Apr 10, 2018 at 3:30

Sagar

25k4 gold badges69 silver badges67 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

mianlaoshu Over a year ago

thanks for this info. I don't know this before. Is there any further info about "Application object still persists since it will be the last object to be deallocated"?

Sagar Over a year ago

You can refer here which says: The Application class, or your subclass of the Application class, is instantiated before any other class when the process for your application/package is created.

mianlaoshu Over a year ago

yes. But what I want to know more is about the application as the last object to be deallocated:)

Sagar Over a year ago

You can refer this article for it

Collectives™ on Stack Overflow

Android:why static variable is set to null on Activity onCreate

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related