java.lang.RuntimeException - What causes this error?
1 2 3 4 5 | java.lang.RuntimeException: createWindowSurface failed at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:701) at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:725) at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:948) at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:825) |
I keep getting this error report frequently in my Play Store portal..
Any ideas why this occurs?
Replies
Umm.. I THINK so.. but I'm not sure..
Let me upload a new version using the latest daily build and see if the error still occurs..
Thanks!
Umm.. I THINK so.. but I'm not sure..
Let me upload a new version using the latest daily build and see if the error still occurs..
Thanks!
Can you also tell us the make and model of the device that this exception occurred on please?
I believe Google Play provides this information.
This way we can confirm that our fix addresses this specific device. Thanks!
OK.. some of the latest error reports are from devices
LG-P920
LG-P925
And the other reports say
OTHER.
Don't know how to see the names of the other devices..
BTW the new design of the developer console doesn't have any way to view the devices where crashes occurred..
Had to switch back to the old design to see the crashes..
And also a similar error
1 2 3 4 | java.lang.RuntimeException: createContext failed at android.opengl.derived.SwapGLSurfaceView$EglHelper.start(SwapGLSurfaceView.java:666) at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:880) at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:825) |
this occurred on VTAB1008..
I experience the same issue, BUT i am on build 984. I will release with 986 then and report back.
Satheesh,
The "createWindowSurface" crash was known to happen on some devices using GPU "PowerVR SGX 540" such as LGs (but not on Kindle Fires and Nooks). We fixed this issue in daily build #986.
So, was this error generated by a daily build older than #986?