Android Failed to initialize display event receiver
My application crashed when I open it again after closing it for quite
some time. The crash report shows this error:
java.lang.RuntimeException: Failed to initialize display event receiver.
status=-2147483648
at android.view.DisplayEventReceiver.nativeInit(Native Method)
at android.view.DisplayEventReceiver.<init>(DisplayEventReceiver.java:61)
at
android.view.Choreographer$FrameDisplayEventReceiver.<init>(Choreographer.java:676)
at android.view.Choreographer.<init>(Choreographer.java:165)
at android.view.Choreographer.<init>(Choreographer.java:68)
at android.view.Choreographer$1.initialValue(Choreographer.java:94)
at android.view.Choreographer$1.initialValue(Choreographer.java:87)
at java.lang.ThreadLocal$Values.getAfterMiss(ThreadLocal.java:430)
at java.lang.ThreadLocal.get(ThreadLocal.java:65)
at android.view.Choreographer.getInstance(Choreographer.java:184)
at android.view.ViewRootImpl.<init>(ViewRootImpl.java:440)
at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:322)
at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:234)
at
android.view.WindowManagerImpl$CompatModeWrapper.addView(WindowManagerImpl.java:153)
at android.view.Window$LocalWindowManager.addView(Window.java:559)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2702)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2140)
at android.app.ActivityThread.access$700(ActivityThread.java:140)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1237)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4921)
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:1038)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
at dalvik.s
I am cracking my head looking for the solution or at least someone with
similar problem but surprisingly there is none. Thanks.
No comments:
Post a Comment