Android異常一、非同步任務導致的視窗控制代碼洩漏問題（記憶體洩漏）
阿新 • • 發佈：2019-01-25
首先來看一下報錯日誌：
05-05 10:36:41.009: E/WindowManager(4243): Activity com.tao.MyActivity has leaked window [email protected] that was originally added here 05-05 10:36:41.009: E/WindowManager(4243): android.view.WindowLeaked: Activity com.tao.MyActivity has leaked window [email protected] that was originally added here 05-05 10:36:41.009: E/WindowManager(4243): at android.view.ViewRoot.<init>(ViewRoot.java:265) 05-05 10:36:41.009: E/WindowManager(4243): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:148) 05-05 10:36:41.009: E/WindowManager(4243): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:91) 05-05 10:36:41.009: E/WindowManager(4243): at android.view.Window$LocalWindowManager.addView(Window.java:424) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.Dialog.show(Dialog.java:241) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ProgressDialog.show(ProgressDialog.java:107) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ProgressDialog.show(ProgressDialog.java:95) 05-05 10:36:41.009: E/WindowManager(4243): at com.unifable.activity.MySecretaryActivity.onCreate(MySecretaryActivity.java:50) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1611) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1663) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ActivityThread.access$1500(ActivityThread.java:117) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:931) 05-05 10:36:41.009: E/WindowManager(4243): at android.os.Handler.dispatchMessage(Handler.java:99) 05-05 10:36:41.009: E/WindowManager(4243): at android.os.Looper.loop(Looper.java:130) 05-05 10:36:41.009: E/WindowManager(4243): at android.app.ActivityThread.main(ActivityThread.java:3683) 05-05 10:36:41.009: E/WindowManager(4243): at java.lang.reflect.Method.invokeNative(Native Method) 05-05 10:36:41.009: E/WindowManager(4243): at java.lang.reflect.Method.invoke(Method.java:507) 05-05 10:36:41.009: E/WindowManager(4243): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:906) 05-05 10:36:41.009: E/WindowManager(4243): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:664) 05-05 10:36:41.009: E/WindowManager(4243): at dalvik.system.NativeStart.main(Native Method) 這是在做一個專案的時候遇到的問題：在第一介面的Activity中，為了避免程式網路慢時，帶來的糟糕的使用者體驗，所以採用非同步任務AsyncTask來訪問網路，與伺服器進行互動，並用 ProgressDialog控制元件來告知使用者當前的程式進度，
在非同步任務裡面已經發生了嚴重的錯誤，而導致Activity的強制關閉。Activity強制關閉了，可是ProgressDialog並沒有dismiss()掉，所以出現了
視窗控制代碼的洩漏。 而且，更嚴重的是，這個異常會覆蓋我們在AsyncTask裡面發生的真正異常，這往往會誤導我們，把過多的精力放在查詢所謂的記憶體洩漏的上面，而不是查詢AsyncTask
中出現的錯誤。