mapbox-maps-android
mapbox-maps-android copied to clipboard
mapbox
Got crash: Reason: executing service com.packagename/com.mapbox.common.LifecycleService
Environment
- Android OS version: 14
- Devices affected: Tested on Pixel 6
- Maps SDK Version: 11.4.1
Observed behavior and steps to reproduce
This is ANR (Application Not Responsing), it pops up
Got error:
Reason: executing service com.packagename/com.mapbox.common.LifecycleService
This happens after upgrading:
implementation 'com.google.android.gms:play-services-location:20.0.0'
to
implementation 'com.google.android.gms:play-services-location:21.3.0'
Expected behavior
To not crash
Additional links and references
Gradle wrapper: 8.7 AGP: 8.5.0 Kotlin: 1.9.0
Full error log:
ANR in com.packagename
PID: 32341
Reason: executing service com.packagename/com.mapbox.common.LifecycleService
ErrorId: effa3f06-efcd-499d-9a04-10ea95becc79
Frozen: false
Load: 5.3 / 4.51 / 4.72
----- Output from /proc/pressure/memory -----
some avg10=0.61 avg60=1.44 avg300=0.46 total=1764207264
full avg10=0.11 avg60=0.24 avg300=0.07 total=590761870
----- End output from /proc/pressure/memory -----
----- Output from /proc/pressure/cpu -----
some avg10=11.37 avg60=14.46 avg300=9.90 total=26965815596
----- End output from /proc/pressure/cpu -----
----- Output from /proc/pressure/io -----
some avg10=0.72 avg60=0.94 avg300=0.29 total=1640043785
full avg10=0.09 avg60=0.24 avg300=0.07 total=888714442
----- End output from /proc/pressure/io -----
CPU usage from 55594ms to -17ms ago (2024-07-13 16:36:54.865 to 2024-07-13 16:37:50.476):
44% 1570/system_server: 31% user + 13% kernel / faults: 156264 minor 414 major
29% 7265/com.android.vending: 26% user + 2.5% kernel / faults: 76838 minor 619 major
13% 598/surfaceflinger: 8.8% user + 4.5% kernel / faults: 883 minor 12 major
8.3% 2066/com.android.systemui: 5.1% user + 3.2% kernel / faults: 11325 minor 325 major
7.2% 3913/com.teslacoilsw.launcher: 4.8% user + 2.4% kernel / faults: 9295 minor 231 major
5.6% 23329/com.google.android.googlequicksearchbox:search: 4.2% user + 1.4% kernel / faults: 54972 minor 1487 major
1.8% 93/kswapd0: 0% user + 1.8% kernel
4.9% 25786/com.google.android.gms.persistent: 3.3% user + 1.5% kernel / faults: 19242 minor 197 major
0.1% 8101/com.google.android.apps.wellbeing: 0.1% user + 0% kernel / faults: 31268 minor 1923 major
4.3% 11692/com.google.android.googlequicksearchbox:interactor: 2.6% user + 1.6% kernel / faults: 42871 minor 4010 major
42% TOTAL: 28% user + 11% kernel + 0.5% iowait + 1.2% irq + 0.6% softirq
CPU usage from 83ms to 855ms later (2024-07-13 16:37:50.541 to 2024-07-13 16:37:51.314):
136% 1570/system_server: 74% user + 62% kernel / faults: 4816 minor 31 major
81% 1664/Signal Catcher: 56% user + 24% kernel
45% 32556/AnrAuxiliaryTas: 13% user + 31% kernel
1.4% 1981/NetworkStats: 1.4% user + 0% kernel
1.4% 32555/AnrConsumer: 1.4% user + 0% kernel
1.3% 49/rcuog/4: 0% user + 1.3% kernel
1.3% 50/rcuop/4: 0% user + 1.3% kernel
1.3% 57/rcuop/5: 0% user + 1.3% kernel
1.3% 64/rcuop/6: 0% user + 1.3% kernel
1.3% 413/sched_pmu_wq: 0% user + 1.3% kernel
1.3% 551/sugov:0: 0% user + 1.3% kernel
1.3% 553/sugov:6: 0% user + 1.3% kernel
1.4% 1139/dhd_rpm_state_t: 0% user + 1.4% kernel
1.4% 1266/adbd: 0% user + 1.4% kernel / faults: 2 minor
1.4% 1266/adbd: 0% user + 1.4% kernel
1.4% 2066/com.android.systemui: 0% user + 1.4% kernel / faults: 1 minor
2.4% 7526/com.sina.weibo: 2.4% user + 0% kernel
2.4% 7788/record_time_upd: 2.4% user + 0% kernel
2.4% 8457/com.sina.weibo:remote: 2.4% user + 0% kernel
3% 24715/process-tracker: 0% user + 3% kernel
3% 26435/com.apkpure.aegon: 0% user + 3% kernel / faults: 2 minor
3% 5076/pool-159-thread: 3% user + 0% kernel
22% TOTAL: 10% user + 10% kernel + 0.1% iowait + 0.4% irq + 0.3% softirq
@donenoyes please share more information: full tombstone file, is this reproducible or occasional, code snippet of how to reproduce it if this is possible.
Encountered the same problem. From testing, it seems to be related to Firebase initialization.
