The application gets quite a few crashes with the next stack trace
java.lang.RuntimeException:
at android.app.LoadedApk.makeApplication(LoadedApk.java:563)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4530)
at android.app.ActivityThread.access$1500(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1364)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5258)
at java.lang.reflect.Method.invoke(Native Method:0)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:940)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:735)
Caused by: java.lang.IllegalStateException:
at android.app.LoadedApk.initializeJavaContextClassLoader(LoadedApk.java:409)
at android.app.LoadedApk.makeApplication(LoadedApk.java:555)
The stack trace has no traces of application code. Given the large user base, it is relatively rare (about 1 in 10 thousand active devices per day). I can not understand any clues from the above information. Can anyone shed some light on this to prevent this collapse?
Edit (2017-06-14): The following screenshot of the Google Play Console shows that in the top 6 failure clusters there is no application code in the stack trace:

java.lang.IllegalArgumentException in android.view.WindowManagerGlobal.findViewLocked
java.lang.IllegalArgumentException in android.view.WindowManagerGlobal.findViewLocked
java.lang.IllegalArgumentException in android.view.WindowManagerGlobal.findViewLocked
in tgkill
in tgkill
java.lang.IllegalStateException
android.app.LoadedApk.initializeJavaContextClassLoader