Closed FSchmitthammer closed 8 years ago
Another had a similar issue with Nexus 6p and I too had an issue with a Nexus 6 is recently acquired.
Without seeing your logs (always post logs), the problem in both cases was Chrome.
Here's the confirmed bug
The user who reported his Nexus 6p crash sent me a log that included this:
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : Build fingerprint: 'google/angler/angler:6.0.1/MMB29P/2473553:user/release-keys'
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : Revision: '0'
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : ABI: 'arm64'
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : pid: 20591, tid: 20642, name: Chrome_InProcGp >>> com.transistorsoft.background_geolocation.ionic <<<
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x440
02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x0 00000000000006d8 x1 0000000000000000 x2 0000000000000000 x3 0000000000000001
02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x4 0000000000000010 x5 0000000000000000 x6 0000000000000010 x7 0000000000000007
02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x8 00000000ffffffff x9 0000000000000010 x10 00000000ffffffff x11 0000000000000000
02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x12 0000000000000000 x13 0000000000000036 x14 00000000000000a2 x15 0000007f50e7ca20
02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x16 0000007f50e7c090 x17 0000000000000003 x18 0000000000000001 x19 0000000000000a20
02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x20 0000007f52242300 x21 0000000000000004 x22 0000007f50e42000 x23 0000007f50e45000
02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x24 0000007f50e45cb8 x25 0000000000000001 x26 0000000000000000 x27 0000007f7ad600f0
02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x28 0000007f5237eb5c x29 0000007f5237e8b0 x30 0000007f7f67e050
02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : sp 0000007f5237e8b0 pc 0000007f7f731624 pstate 0000000060000000
02-05 14:33:11.686 /system/bin/debuggerd64(3323) - F DEBUG :
02-05 14:33:11.686 /system/bin/debuggerd64(3323) - F DEBUG : backtrace:
02-05 14:33:11.687 /system/bin/debuggerd64(3323) - F DEBUG : #00 pc 000000000024d624 /vendor/lib64/egl/libGLESv2_adreno.so (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, EsxAccessType)+64)
02-05 14:33:11.687 /system/bin/debuggerd64(3323) - F DEBUG : #01 pc 000000000019a04c /vendor/lib64/egl/libGLESv2_adreno.so
The interesting lines are here:
/vendor/lib64/egl/libGLESv2_adreno.so (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, EsxAccessType)+64)
02-05 14:33:11.687 /system/bin/debuggerd64(3323) - F DEBUG : #01 pc 000000000019a04c /vendor/lib64/egl/libGLESv2_adreno.so
Thank you chris. That is what is happening. It is crashing.
Regards, Fred Schmitthammer (562)307-0219 (623)258-4400
On Fri, Mar 4, 2016 at 7:16 AM, Chris Scott notifications@github.com wrote:
Here's the confirmed bug https://issues.apache.org/jira/browse/CB-10054
The user who reported his Nexus 6p crash sent me a log that included this:
02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : * * * * * * * * * * * * * * * * 02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : Build fingerprint: 'google/angler/angler:6.0.1/MMB29P/2473553:user/release-keys' 02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : Revision: '0' 02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : ABI: 'arm64' 02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : pid: 20591, tid: 20642, name: Chrome_InProcGp >>> com.transistorsoft.background_geolocation.ionic <<< 02-05 14:33:11.651 /system/bin/debuggerd64(3323) - F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x440 02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x0 00000000000006d8 x1 0000000000000000 x2 0000000000000000 x3 0000000000000001 02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x4 0000000000000010 x5 0000000000000000 x6 0000000000000010 x7 0000000000000007 02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x8 00000000ffffffff x9 0000000000000010 x10 00000000ffffffff x11 0000000000000000 02-05 14:33:11.684 /system/bin/debuggerd64(3323) - F DEBUG : x12 0000000000000000 x13 0000000000000036 x14 00000000000000a2 x15 0000007f50e7ca20 02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x16 0000007f50e7c090 x17 0000000000000003 x18 0000000000000001 x19 0000000000000a20 02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x20 0000007f52242300 x21 0000000000000004 x22 0000007f50e42000 x23 0000007f50e45000 02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x24 0000007f50e45cb8 x25 0000000000000001 x26 0000000000000000 x27 0000007f7ad600f0 02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : x28 0000007f5237eb5c x29 0000007f5237e8b0 x30 0000007f7f67e050 02-05 14:33:11.685 /system/bin/debuggerd64(3323) - F DEBUG : sp 0000007f5237e8b0 pc 0000007f7f731624 pstate 0000000060000000 02-05 14:33:11.686 /system/bin/debuggerd64(3323) - F DEBUG : 02-05 14:33:11.686 /system/bin/debuggerd64(3323) - F DEBUG : backtrace: 02-05 14:33:11.687 /system/bin/debuggerd64(3323) - F DEBUG : #00 pc 000000000024d624 /vendor/lib64/egl/libGLESv2_adreno.so (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, EsxAccessType)+64) 02-05 14:33:11.687 /system/bin/debuggerd64(3323) - F DEBUG : #01 pc 000000000019a04c /vendor/lib64/egl/libGLESv2_adreno.so
The interesting lines are here:
/vendor/lib64/egl/libGLESv2_adreno.so (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, EsxAccessType)+64) 02-05 14:33:11.687 /system/bin/debuggerd64(3323) - F DEBUG : #01 pc 000000000019a04c /vendor/lib64/egl/libGLESv2_adreno.so
— Reply to this email directly or view it on GitHub https://github.com/transistorsoft/cordova-background-geolocation-SampleApp/issues/34#issuecomment-192317862 .
Ok, closing this. It's a WebView issue -- not an issue with the plugin. Let me know how you fixed it.
For my Nexus 6, I got the crash when I upgraded the WebView. I solved it by doing a factory reset.
We will be adding some default webview settings as recommended in this link:
https://cordova.apache.org/docs/en/latest/guide/platforms/android/webview.html
Regards, Fred Schmitthammer (562)307-0219 (623)258-4400
On Fri, Mar 4, 2016 at 11:56 AM, Chris Scott notifications@github.com wrote:
Closed #34 https://github.com/transistorsoft/cordova-background-geolocation-SampleApp/issues/34 .
— Reply to this email directly or view it on GitHub https://github.com/transistorsoft/cordova-background-geolocation-SampleApp/issues/34#event-578285721 .
I have compiled and installed the demo application with no issue on Android Version 5. If I take the same and install it on my Nexus 6p running Marshmallow the app installs but crashes right after it runs. The app does have the proper permissions.