android.view.WindowManager$BadTokenException

[Meeh]

android.view.WindowManager$BadTokenException: 
  at android.view.ViewRootImpl.setView (ViewRootImpl.java:951)
  at android.view.WindowManagerGlobal.addView (WindowManagerGlobal.java:356)
  at android.view.WindowManagerImpl.addView (WindowManagerImpl.java:94)
  at android.app.Dialog.show (Dialog.java:329)
  at net.i2p.android.router.web.I2PWebViewClient$BackgroundEepLoad.onProgressUpdate (I2PWebViewClient.java:424)
  at net.i2p.android.router.web.I2PWebViewClient$BackgroundEepLoad.onProgressUpdate (I2PWebViewClient.java:306)
  at android.os.AsyncTask$InternalHandler.handleMessage (AsyncTask.java:715)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:193)
  at android.app.ActivityThread.main (ActivityThread.java:6863)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:537)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

[zzz]

dups: #2320 #2480

this is through the problematic WebViewClient?.

possible clues:

​https://stackoverflow.com/questions/6977771/windowmanagerbadtokenexception

[Meeh]

This is the far most triggered bug the past release.

[Meeh]

16 times the past 60 days.

[zzz]

Catch RuntimeException? which is what WindowManager?$BadTokenException? extends
in 34e59a6bfece57da13f9fb9b2714fef9ff971b09 to be 0.9.41

[zzz]

Note that this only catches the crash. Not clear if we're using the wrong context when creating the ProgressDialog? at line 114. See also SO link in comment 1. Perhaps we should be using the static ProgressDialog?.show() instead?