-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Android - continual loading of map kills app #4224
Comments
This will not resolve the mentioned crash but why not leverage the power of the |
Looking at the stacktrace show above, it's allmost the same as: 03-07 21:16:15.396 21751-25248/? A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 25248 (Thread-8162)
03-07 21:16:15.513 201-201/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-07 21:16:15.514 201-201/? A/DEBUG: Build fingerprint: 'google/hammerhead/hammerhead:6.0/MPA44I/2172151:user/release-keys'
03-07 21:16:15.514 201-201/? A/DEBUG: Revision: '0'
03-07 21:16:15.514 201-201/? A/DEBUG: ABI: 'arm'
03-07 21:16:15.515 201-201/? A/DEBUG: pid: 21751, tid: 25248, name: Thread-8162 >>> com.mapbox.mapboxsdk.testapp <<<
03-07 21:16:15.515 201-201/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-07 21:16:15.539 201-201/? A/DEBUG: r0 00000000 r1 000062a0 r2 00000006 r3 9c4bf978
03-07 21:16:15.539 201-201/? A/DEBUG: r4 9c4bf980 r5 9c4bf930 r6 00000000 r7 0000010c
03-07 21:16:15.540 201-201/? A/DEBUG: r8 9ca54988 r9 9bbf76a0 sl fffff484 fp 9c4bf3c8
03-07 21:16:15.540 201-201/? A/DEBUG: ip 00000006 sp 9c4bf368 lr b6cbbaf1 pc b6cbde54 cpsr 400d0010
03-07 21:16:15.559 201-201/? A/DEBUG: backtrace:
03-07 21:16:15.560 201-201/? A/DEBUG: #00 pc 00041e54 /system/lib/libc.so (tgkill+12)
03-07 21:16:15.560 201-201/? A/DEBUG: #01 pc 0003faed /system/lib/libc.so (pthread_kill+32)
03-07 21:16:15.560 201-201/? A/DEBUG: #02 pc 0001c30f /system/lib/libc.so (raise+10)
03-07 21:16:15.560 201-201/? A/DEBUG: #03 pc 000194c1 /system/lib/libc.so (__libc_android_abort+34)
03-07 21:16:15.560 201-201/? A/DEBUG: #04 pc 000174ac /system/lib/libc.so (abort+4)
03-07 21:16:15.560 201-201/? A/DEBUG: #05 pc 003f1a60 /data/app/com.mapbox.mapboxsdk.testapp-2/lib/arm/libmapbox-gl.so
03-07 21:16:15.560 201-201/? A/DEBUG: #06 pc 003f1b90 /data/app/com.mapbox.mapboxsdk.testapp-2/lib/arm/libmapbox-gl.so
03-07 21:16:15.560 201-201/? A/DEBUG: #07 pc 003e21e8 /data/app/com.mapbox.mapboxsdk.testapp-2/lib/arm/libmapbox-gl.so
03-07 21:16:15.560 201-201/? A/DEBUG: #08 pc 003e22d4 /data/app/com.mapbox.mapboxsdk.testapp-2/lib/arm/libmapbox-gl.so (std::terminate()+136)
03-07 21:16:15.560 201-201/? A/DEBUG: #09 pc 000e44bc /data/app/com.mapbox.mapboxsdk.testapp-2/lib/arm/libmapbox-gl.so I can reproduce this fairly easy if I back press 2 stacked activities quickly. |
I'm currently testing out the fix proposed in #2995 (comment) |
Thanks @tobrun for sorting that! re day and night - totally agree, it would be awesome to automagically change the theme for day and night - certainly if it was my app. Regardless, I'll try and dig through some of the appcompat code to see whether we could have several themes available to switch at runtime and use in combination with a layer switcher. We certainly have day and night map styles but also some maps are high contrast with pretty random colors - where we need to set a theme specific for the layer...others like satellite could do with a sample from the map to work out what looks good (e.g. desert vs rainforest). |
@snodnipper finish();
startActivity(new Intent(MainActivity.this, MainActivity.class)); I'm currently not able to produce any crashes with current state of master. |
@snodnipper |
That is looking pretty stable - I haven't crashed it yet in my emulator. We'll give it a go on some real devices but it appears solved to me. Really well done. I'll take a look at the project tonight and pull out any work-arounds. |
@snodnipper |
I have a demo app that styles the map according to the Android theme. When we press the layer button, we have to restart the activity to ensure that all the chrome (buttons etc.) is styled correctly.
After about 10 change style clicks we end up with the blow-up below. This may be related to #2995
This was captured from an HTC M8 but I will check other devices.
Turning off StrictMode still results in a crash.
The text was updated successfully, but these errors were encountered: