Java Question

Unknown crash report android

I have released an app on Google play store and started rolling out updates, the latest one seemed to worked fine until I received this crash report from a user
can anyone help me figure out what it is exactly, what caused it and the possible ways of fixing it ?

Device info: Asus ZenFone 2 (ZE500CL) (ASUS_Z00D), 2048MB RAM, Android 5.0

native: pc 0000000000090df6 /system/lib/ (tgkill+22)
native: pc 0000000000038d13 /system/lib/ (pthread_kill+163)
native: pc 000000000003a5f5 /system/lib/ (raise+37)
native: pc 0000000000032855 /system/lib/ (abort+85)
native: pc 00000000000104da /system/vendor/lib/ (PVRSRVDebugAssertFail+58)
native: pc 0000000000006e82 /system/vendor/lib/egl/
native: pc 000000000001b576 /system/vendor/lib/egl/
native: pc 000000000001b6d1 /system/vendor/lib/egl/
native: pc 0000000000009d72 /system/vendor/lib/
native: pc 000000000000fcea /system/vendor/lib/ (IMGeglMakeCurrent+1514)
native: pc 00000000000015a3 /system/vendor/lib/egl/ (eglMakeCurrent+51)
native: pc 000000000001133f /system/lib/ (android::egl_display_t::makeCurrent(android::egl_context_t*, android::egl_context_t*, void*, void*, void*, void*, void*, void*)+303)
native: pc 0000000000014e3b /system/lib/ (eglMakeCurrent+635)
native: pc 0000000000087fce /system/lib/
native: pc 000000000008247f /system/lib/
native: pc 0000000000088b24 /system/lib/
native: pc 0000000000088623 /system/lib/
native: pc 000000000008b55a /system/lib/ (android::uirenderer::renderthread::RenderThread::threadLoop()+154)
native: pc 0000000000016ece /system/lib/ (android::Thread::_threadLoop(void*)+398)
native: pc 0000000000071d23 /system/lib/ (android::AndroidRuntime::javaThreadShell(void*)+99)
native: pc 00000000000165cb /system/lib/ (thread_data_t::trampoline(thread_data_t const*)+123)
native: pc 0000000000037cdb /system/lib/ (__pthread_start(void*)+59)
native: pc 0000000000032fba /system/lib/ (__start_thread+26)
native: pc 0000000000011df6 /system/lib/ (__bionic_clone+70)

Answer Source

That's a native crash meaning a bug that was in the user's device itself not a bug in your code. I don't know what's the bug though, but that's what it means. I, personally, sometimes ignore these types of crashes if they don't occur too much. But if it occurs again and again, then you will have to see what new code you added in your new version and try to find out what was causing this issue by removing parts of your new code part by part and test it on the same device until you find it out. Unfortunately, you may not have the same device, but that's the way to fix this if it's really needed.