12-07 11:13:14.030 13836-13836/com.xxx.xxx.android E/error.out: 檢測到嚴重錯誤，程序即將退出
java.lang.RuntimeException: Unable to destroy activity {com.xxx.xxx.android/com.xxx.xxx.android.activity.chat.ChatActivity}: java.lang.IllegalStateException: Activity has been destroyed
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3271)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3289)
at android.app.ActivityThread.access$1200(ActivityThread.java:134)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1280)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:4624)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:809)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:576)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.IllegalStateException: Activity has been destroyed
at android.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1286)
at android.app.BackStackRecord.commitInternal(BackStackRecord.java:541)
at android.app.BackStackRecord.commitAllowingStateLoss(BackStackRecord.java:529)
at com.bumptech.glide.manager.RequestManagerRetriever.getRequestManagerFragment(RequestManagerRetriever.java:159)
at com.bumptech.glide.manager.RequestManagerRetriever.fragmentGet(RequestManagerRetriever.java:168)
at com.bumptech.glide.manager.RequestManagerRetriever.get(RequestManagerRetriever.java:127)
at com.bumptech.glide.Glide.with(Glide.java:632)
at com.xxx.xxx.android.activity.BaseActivity.onDestroy(BaseActivity.java:399)
at com.xxx.xxx.android.activity.socketservice.SocketServiceActivity.onDestroy(SocketServiceActivity.java:157)
at com.xxx.xxx.android.activity.chat.ChatActivity.onDestroy(ChatActivity.java:3607)
at android.app.Activity.performDestroy(Activity.java:4643)
at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1081)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3258)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3289)?
at android.app.ActivityThread.access$1200(ActivityThread.java:134)?
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1280)?
at android.os.Handler.dispatchMessage(Handler.java:99)?
at android.os.Looper.loop(Looper.java:154)?
at android.app.ActivityThread.main(ActivityThread.java:4624)?
at java.lang.reflect.Method.invokeNative(Native Method)?
at java.lang.reflect.Method.invoke(Method.java:511)?
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:809)?
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:576)?
at dalvik.system.NativeStart.main(Native Method)?
出現的原因
This seems to be a bug in the newly added support for nested fragments. Basically, the child FragmentManager ends up with a broken internal state when it is detached from the activity. A short-term workaround that fixed it for me is to add the following to onDetach() of every Fragment which you call getChildFragmentManager() on:
解決方法
- stackoverflow上面給的解決辦法是重寫onDetach方法，測試行不通
@Override
public void onDetach() {
super.onDetach();
try {
Field childFragmentManager = Fragment.class.getDeclaredField("mChildFragmentManager");
childFragmentManager.setAccessible(true);
childFragmentManager.set(this, null);
} catch (NoSuchFieldException e) {
throw new RuntimeException(e);
} catch (IllegalAccessException e) {
throw new RuntimeException(e);
}
}- 在使用該Viewpager的Fragment中，重寫方法onDestroyView()，測試有效
@Override
public void onDestroyView() {
super.onDestroyView();
try {
Field childFragmentManager = Fragment.class.getDeclaredField("mChildFragmentManager");
childFragmentManager.setAccessible(true);
childFragmentManager.set(this, null);
} catch (NoSuchFieldException e) {
throw new RuntimeException(e);
} catch (IllegalAccessException e) {
throw new RuntimeException(e);
}
}爲什麼在onDetach行不通呢，因爲按照Activity跟Fragment的生命週期圖來看，onDetach階段Fragment已經與Activity脫離關係——即Fragment持有的Activity對象已被置null，而onDestroyView階段Fragment中仍然保留與Activity之間的關係,此時Fragment持有的Activity對象仍然有效。
