目前在我的代码库中我有以下类(部分内容),它显示了2个内存泄漏消息"不要将Android上下文类放在静态字段中(对具有指向Context的字段上下文的Myclass的静态引用);这是一个内存泄漏(也打破了瞬间运行)" 我不确定替代方案是什么。这是100%的内存泄漏吗?我在" INSTANCE上得到了泄漏警告;"和"静态"上下文声明。知道怎么去修理吗?
public enum Myclass {
INSTANCE;
public static final boolean TLS_ENABLED = true;
private static final String TAG = Myclass.class.getSimpleName();
private static final String SP = "My_class";
private static Context context;
public void init(Context context, String appKey, String appSecret) {
init(context, null, appKey, appSecret);
}
/**
* Initialize class
*
* @param context Application level context.
* @param apiUrl API url of backend server
* @param appKey Application key
* @param appSecret Application secret
* @throws IllegalArgumentException If activity instance will be passed as the context
* @throws IllegalArgumentException If application key is empty or null
* @throws IllegalArgumentException If application secret is empty or null
*/
public void init(Context context, String apiUrl, String appKey, String appSecret) {
if (null == context) { throw new NullPointerException(); }
if (!(context instanceof Application)) { throw new IllegalArgumentException("Supply my class with application context"); }
// if (TextUtils.isEmpty(apiUrl)) { throw new IllegalArgumentException("Api url can't be null or empty string"); }
if (TextUtils.isEmpty(appKey)) { throw new IllegalArgumentException("App key can't be null or empty string"); }
if (TextUtils.isEmpty(appSecret)) { throw new IllegalArgumentException("App secret can't be null or empty string"); }
this.apiUrl = apiUrl;
this.appKey = appKey;
this.appSecret = appSecret;
this.sp = context.getSharedPreferences(SP, Context.MODE_PRIVATE);
MyClass.context = context;
initManagers();
}
/**
* Initializes managers. This method must be called after constructor
* returns, as the managers during own initialization may use myclass.get()
* method.
*/
private void initManagers() {
accountManager = new AccountManager();
myclassApi = new MyclassApi(context, apiUrl);
contactManager = new ContactManager();
connectionManager = new ConnectionManager();
meetingListManager = new MeetingListManager();
}
/**
* Returns {@link Context} that was passed to
* {@link myclass#init(Context, String, String)}.
*
* @return
*/
public static Context getContext() {
return context;
}
/**
* Returns {@link SharedPreferences} instance.
*
* @return SharedPreferences
*/
public SharedPreferences getSp() {
return this.sp;
}
public static class Event<T> {
private State state = State.SUCCESS;
private Throwable t;
private T data;
private String errorMessage;
/**
* Event state. If event related to network request/response
* operations - state indicates the physical (not logical)
* success or fail of request.
*/
public enum State {
/**
* Indicates that attempt to get data or perform task successful
*/
SUCCESS,
/**
* Indicates that attempt to get data or perform task fails,
* and reason of fail is the incorrect request data
*/
FAIL,
/**
* Indicates that attempt to get data or perform task encounter an error
* mostly due to connection problem
*/
ERROR,
/**
* Indicates that attempt to get data or perform task was ignored
* according to internal state of event producer.
*/
IGNORED
}
}
答案 0 :(得分:1)
安全将应用程序上下文存储在静态字段中,您可以在将其存储到静态字段之前对所获得的任何上下文引用进行简单的调用context.getApplicationContext()
。
无论如何,应用程序上下文都是单例,你不能泄漏它。
答案 1 :(得分:1)
如果您确定上下文只存储ApplicationContext,而不是Activity上下文,您可以使用注释来抑制此警告,这似乎是来自IDE的警告。
@SuppressLint("StaticFieldLeak")
如果您想了解更多有关内存泄漏的信息,可以查看我唯一的博客:) here