search

streetcomplete / StreetComplete

Easy to use OpenStreetMap editor for Android
https://streetcomplete.app
GNU General Public License v3.0
3.91k stars 358 forks source link

location pointer pin crashes on Xiaomi Redmi Note3 (60.0-alpha2) #6001

Closed mnalis closed 8 hours ago

mnalis commented 3 weeks ago

While trying to help debug performance issues in https://github.com/streetcomplete/StreetComplete/issues/5994#issuecomment-2453041453, I've encountered almost immediate crashes with this phone.

I thought of https://github.com/streetcomplete/StreetComplete/issues/5954 / https://github.com/maplibre/maplibre-native/issues/2206, but:

How to Reproduce

Expected Behavior

I'd expect it to not crash. Also of note:

Versions affected 60.0-alpha2, Android 6.0.1 on Xiaomi Redmi Note 3

mnalis commented 3 weeks ago

That phone does not have screen recorder, so had to use another phone to record it... Here is SC crashing after few seconds of panning:

https://github.com/user-attachments/assets/a124772b-228f-4c66-89bb-c2862e428c66

and here is SCEE on the same area with about same amount of data loaded, working just fine:

https://github.com/user-attachments/assets/cf53aaca-7641-4f72-9859-9c61f6b5ab86

I switched between several times, and always SC 6.0-alpha2 crashed, and SCEE 59.1 worked.

mnalis commented 3 weeks ago

Don't know if it helps, but I've tried looking up that error - there were not much matches, but those that I found always seemed (e.g. https://github.com/android/sunflower/issues/519 or https://github.com/material-components/material-components-android/issues/661) related to some "0dp" fix MaterialComponents thingies like solved here: https://stackoverflow.com/questions/36115934/android-opengl-error-during-camera-animation

westnordost commented 3 weeks ago

Uff, a crash in native code, so we can not really fix this here, only try to avoid it occuring, i.e. working around it.

Are you able to post the stack trace here?

mnalis commented 3 weeks ago

Uff, a crash in native code, so we can not really fix this here, only try to avoid it occuring

Yeah, but since it doesn't crash in SCEE 59.1, I'd guess SC 59.1 was also fine, so it should be possible to isolate and then change the factor leading up to the crashes. Do you want me to some more tests on that device?

Are you able to post the stack trace here?

Here it is:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V10.2.1.0.MHOMIXM:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 23297, tid: 23358, name: hwuiTask2  >>> de.westnordost.streetcomplete <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'Error: Spot pair overflow!!! used 171, total 108'
    x0   0000000000000000  x1   0000000000005b3e  x2   0000000000000006  x3   0000000000000000
    x4   0000000000000000  x5   0000000000000001  x6   0000000000000000  x7   0000000000000000
    x8   0000000000000083  x9   0000007fad6fe012  x10  0000000000000000  x11  0000007fad6fd000
    x12  0000007fad6e8090  x13  0000000000000000  x14  0000007fad6fd000  x15  0000007fad6e8158
    x16  0000007fb080a6a8  x17  0000007fb07ccbdc  x18  0000007fad6fd000  x19  0000007f8a490510
    x20  0000007f8a490450  x21  0000000000000000  x22  0000000000000006  x23  00000000000000ab
    x24  000000000000001b  x25  00000000000000ab  x26  00000055b4297760  x27  0000007f8a48f290
    x28  00000000000000ab  x29  0000007f8a48e5a0  x30  0000007fb07ca378
    sp   0000007f8a48e5a0  pc   0000007fb07ccbe4  pstate 0000000020000000

backtrace:
    #00 pc 000000000006abe4  /system/lib64/libc.so (tgkill+8)
    #01 pc 0000000000068374  /system/lib64/libc.so (pthread_kill+68)
    #02 pc 00000000000212f8  /system/lib64/libc.so (raise+28)
    #03 pc 000000000001ba98  /system/lib64/libc.so (abort+60)
    #04 pc 000000000000d328  /system/lib64/libcutils.so (__android_log_assert+236)
    #05 pc 000000000006f168  /system/lib64/libhwui.so
    #06 pc 0000000000074d14  /system/lib64/libhwui.so
    #07 pc 0000001500000087  <unknown>
westnordost commented 3 weeks ago

Thanks! Hmm... not helpful, though.

So the crash does not happen when location is off?

At the moment I have no idea what could cause this. If your view is not glued to the location, the following things should be different as compared to having no location at all:

Since you are currently the only one who can reproduce this, I fear you are currently the only one who can dig down deeper what exactly is causing the crash. So, you could comment out some stuff that is happening when the app has location and run the app again to see if the crash is still reproducible then. E.g. search for intersection in MainScreen to find what to comment out to make the location pointer pin dissapear. The location dot on the map is displayed in CurrentLocationMapComponent. See also MainMapFragment.onLocationChanged. You could add a Log.e("LOCATION", "Got a new Location!") there to see if the crash happens at exactly the time a new location is being received from the system.

mnalis commented 1 week ago

The debug effort so far:

There are only 'skip'ped commits left to test. The first bad commit could be any of: 2c4cb49c221de0b241bb233bd503554aedbc2f33 50abfbba61e69f615dc5ae19bf7074ceb4995970 1f8c5185b38e4137f89add4893b7e7e8606e740f a095b21464e398e90986fca060206936c621e844 e3c8a48b9535d3c237dfb526c6d7aa4888d1c65d f8bb5b1b1e873bf0f19992237e0858a3a2498127 8d2dde061ed910d382463518da5f7daf4f23cf13 We cannot bisect more!

log ``` 11-19 14:08:35.616 4280 4280 W Binder:1474_C: type=1400 audit(0.0:700): avc: denied { ioctl } for path="socket:[69651]" dev="sockfs" ino=69651 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0 11-19 14:08:35.633 8221 8221 E LOCATION: Got a new Location! 11-19 14:08:35.634 8221 8221 E LOCATION: Got a new Location! 11-19 14:08:35.924 7727 7770 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-19 14:08:35.931 8221 8276 I Adreno : QUALCOMM build : a7823f5, I59a6815413 11-19 14:08:35.931 8221 8276 I Adreno : Build Date : 09/23/16 11-19 14:08:35.931 8221 8276 I Adreno : OpenGL ES Shader Compiler Version: XE031.07.00.00 11-19 14:08:35.931 8221 8276 I Adreno : Local Branch : mybranch22028469 11-19 14:08:35.931 8221 8276 I Adreno : Remote Branch : quic/LA.BR.1.3.3_rb2.26 11-19 14:08:35.931 8221 8276 I Adreno : Remote Branch : NONE 11-19 14:08:35.931 8221 8276 I Adreno : Reconstruct Branch : NOTHING 11-19 14:08:35.940 8221 8276 I OpenGLRenderer: Initialized EGL, version 1.4 11-19 14:08:35.976 8221 8273 I Mbgl-EGLConfigChooser: In emulator: false 11-19 14:08:36.014 8221 8277 I Mbgl : {RenderThread 34}[General]: GPU Identifier: Adreno (TM) 510 11-19 14:08:36.015 8221 8273 E HAL : hw_get_module_by_class: module name gralloc 11-19 14:08:36.016 8221 8273 E HAL : hw_get_module_by_class: module name gralloc 11-19 14:08:36.023 8221 8231 I art : Background sticky concurrent mark sweep GC freed 25931(1227KB) AllocSpace objects, 0(0B) LOS objects, 1% free, 44MB/45MB, paused 8.027ms total 70.796ms 11-19 14:08:36.188 1474 1501 I ActivityManager: Displayed de.westnordost.streetcomplete.debug/de.westnordost.streetcomplete.screens.main.MainActivity: +2s9ms 11-19 14:08:36.188 1474 1501 I Timeline: Timeline: Activity_windows_visible id: ActivityRecord{770c26a u0 de.westnordost.streetcomplete.debug/de.westnordost.streetcomplete.screens.main.MainActivity t3346} time:1172767 11-19 14:08:36.186 4283 4283 W Binder:1474_E: type=1400 audit(0.0:701): avc: denied { ioctl } for path="socket:[69670]" dev="sockfs" ino=69670 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0 11-19 14:08:36.186 4283 4283 W Binder:1474_E: type=1400 audit(0.0:702): avc: denied { ioctl } for path="socket:[69670]" dev="sockfs" ino=69670 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0 11-19 14:08:36.193 5063 5170 D PowerKeeper.Event: notifyActivityLaunchTime: de.westnordost.streetcomplete.debug/de.westnordost.streetcomplete.screens.main.MainActivity totalTime: 2009 11-19 14:08:36.186 1485 1485 W Binder:1474_2: type=1400 audit(0.0:703): avc: denied { ioctl } for path="socket:[69669]" dev="sockfs" ino=69669 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0 11-19 14:08:36.186 1485 1485 W Binder:1474_2: type=1400 audit(0.0:704): avc: denied { ioctl } for path="socket:[69669]" dev="sockfs" ino=69669 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0 11-19 14:08:36.204 8221 8221 E LOCATION: Got a new Location! 11-19 14:08:36.208 8221 8221 I QuestAutoSyncer: Checking whether to automatically download new quests at 43.7347070,15.8925410 11-19 14:08:36.219 8221 8231 I art : Background partial concurrent mark sweep GC freed 99032(3MB) AllocSpace objects, 2(1336KB) LOS objects, 27% free, 42MB/58MB, paused 4.558ms total 134.052ms 11-19 14:08:36.381 8221 8221 E Mbgl : {tcomplete.debug}[JNI]: Error setting property: symbol-sort-key layer doesn't support this property 11-19 14:08:36.382 8221 8221 E Mbgl : {tcomplete.debug}[JNI]: Error setting property: icon-allow-overlap layer doesn't support this property 11-19 14:08:36.382 8221 8221 E Mbgl : {tcomplete.debug}[JNI]: Error setting property: icon-ignore-placement layer doesn't support this property 11-19 14:08:36.744 3350 3350 D RecentsActivity: onStop 11-19 14:08:36.745 3350 3350 D EventBus: [3350, u0] send(RecentsVisibilityChangedEvent) 11-19 14:08:36.745 3350 3350 D EventBus: [3350, u0] -> RecentsViewTouchHandler [0x416885c, P4] onBusEvent(RecentsVisibilityChangedEvent) 11-19 14:08:36.745 3350 3350 D EventBus: [3350, u0] onBusEvent(RecentsVisibilityChangedEvent) duration: 11 microseconds, avg: 839 11-19 14:08:36.745 3350 3350 D EventBus: [3350, u0] -> TaskStackView [0xe564961, P3] onBusEvent(RecentsVisibilityChangedEvent) 11-19 14:08:36.745 3350 3350 D EventBus: [3350, u0] unregister() 11-19 14:08:36.747 3350 3350 D EventBus: [3350, u0] unregister() 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] unregister() 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] unregister() 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] onBusEvent(RecentsVisibilityChangedEvent) duration: 2766 microseconds, avg: 852 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] -> RecentMenuView [0x57a9aee, P3] onBusEvent(RecentsVisibilityChangedEvent) 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] onBusEvent(RecentsVisibilityChangedEvent) duration: 7 microseconds, avg: 846 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] -> RecentsImpl [0x95872e3, P1] onBusEvent(RecentsVisibilityChangedEvent) 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] onBusEvent(RecentsVisibilityChangedEvent) duration: 3 microseconds, avg: 841 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] -> Recents [0xd842f59, P1] onBusEvent(RecentsVisibilityChangedEvent) 11-19 14:08:36.748 3350 3350 D EventBus: [3350, u0] onBusEvent(RecentsVisibilityChangedEvent) duration: 15 microseconds, avg: 836 11-19 14:08:38.308 8221 8231 I art : Background sticky concurrent mark sweep GC freed 191429(7MB) AllocSpace objects, 64(3MB) LOS objects, 16% free, 49MB/58MB, paused 3.754ms total 164.800ms 11-19 14:08:38.335 8221 8263 I QuestAutoSyncer: Downloading in radius of 386 meters around user (9 tiles) 11-19 14:08:38.524 8221 8248 I WM-Processor: Moving WorkSpec (97c0c40f-1820-43f9-9518-459f740c7c23) to the foreground 11-19 14:08:38.561 8221 8221 I WM-SystemFgDispatcher: Started foreground service Intent { act=ACTION_START_FOREGROUND cmp=de.westnordost.streetcomplete.debug/androidx.work.impl.foreground.SystemForegroundService (has extras) } 11-19 14:08:38.571 8221 8263 I Download: Starting download (1.8 km², bbox: 43.7274446,15.8862305,43.7393521,15.9027100) 11-19 14:08:38.590 1474 1474 D zhoumingliang: forLEDtest==false 11-19 14:08:38.595 8221 8221 D zhoumingliang: isINtest==false 11-19 14:08:38.602 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] 11-19 14:08:38.605 1474 1474 D zhoumingliang: forLEDtest==false 11-19 14:08:38.613 3350 3350 D StatusBar: addNotification key=0|de.westnordost.streetcomplete.debug|1|null|10202 11-19 14:08:38.618 3350 3350 W ResourceType: No package identifier when getting name for resource number 0x00000000 11-19 14:08:38.630 3350 3350 D StatusBar: No peeking: unimportant notification: 0|de.westnordost.streetcomplete.debug|1|null|10202 11-19 14:08:38.634 8221 8267 W PathParser: Points are too far apart 4.000000165353159 11-19 14:08:38.634 8221 8267 W PathParser: Points are too far apart 4.000000950111488 11-19 14:08:38.644 3350 3350 D StatusBar: addNotification key=0|de.westnordost.streetcomplete.debug|1|null|10202 11-19 14:08:38.654 3350 3350 D StatusBar: No peeking: unimportant notification: 0|de.westnordost.streetcomplete.debug|1|null|10202 11-19 14:08:38.659 8221 8221 V Mbgl-ConnectivityReceiver: connected - true 11-19 14:08:38.664 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:38.665 730 988 W XTCC-5.1.0.13: [CS-RIL-LISTENER] timerCallback fired for ril update registering, re-register 11-19 14:08:38.666 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:38.668 8221 8260 I DpmTcmClient: RegisterTcmMonitor from: com.android.okhttp.TcmIdleTimerMonitor 11-19 14:08:38.759 8221 8221 V Mbgl-ConnectivityReceiver: connected - true 11-19 14:08:38.770 3350 3350 D StatusBar: No peeking: unimportant notification: 0|de.westnordost.streetcomplete.debug|1|null|10202 11-19 14:08:38.790 3350 3350 W View : requestLayout() improperly called by android.widget.DateTimeView{89cbca4 V.ED..... ......ID 745,5-821,46 #102039a android:id/notification_time} during layout: running second layout pass 11-19 14:08:38.849 8221 8231 I art : Background sticky concurrent mark sweep GC freed 191767(7MB) AllocSpace objects, 0(0B) LOS objects, 3% free, 56MB/58MB, paused 1.780ms total 215.966ms 11-19 14:08:38.888 8221 8267 W PathParser: Points are too far apart 4.013171872685047 11-19 14:08:38.889 8221 8267 W PathParser: Points are too far apart 4.013171872685047 11-19 14:08:38.889 8221 8267 W PathParser: Points are too far apart 4.013171872685072 11-19 14:08:38.889 8221 8267 W PathParser: Points are too far apart 4.013171872685072 11-19 14:08:38.889 8221 8267 W PathParser: Points are too far apart 4.013171872685043 11-19 14:08:38.889 8221 8267 W PathParser: Points are too far apart 4.013171872685043 11-19 14:08:38.890 8221 8267 W PathParser: Points are too far apart 4.013171872685078 11-19 14:08:38.890 8221 8267 W PathParser: Points are too far apart 4.013171872685078 11-19 14:08:38.890 8221 8267 W PathParser: Points are too far apart 4.013171872685062 11-19 14:08:38.890 8221 8267 W PathParser: Points are too far apart 4.013171872685062 11-19 14:08:38.891 8221 8267 W PathParser: Points are too far apart 4.013171872685064 11-19 14:08:38.891 8221 8267 W PathParser: Points are too far apart 4.013171872685064 11-19 14:08:38.892 8221 8267 W PathParser: Points are too far apart 4.01317547145789 11-19 14:08:38.892 8221 8267 W PathParser: Points are too far apart 4.01317547145789 11-19 14:08:38.892 8221 8267 W PathParser: Points are too far apart 4.01317547145789 11-19 14:08:38.892 8221 8267 W PathParser: Points are too far apart 4.01317547145789 11-19 14:08:38.893 8221 8267 W PathParser: Points are too far apart 4.013175471457849 11-19 14:08:38.893 8221 8267 W PathParser: Points are too far apart 4.013175471457849 11-19 14:08:38.894 8221 8267 W PathParser: Points are too far apart 4.013175471457885 11-19 14:08:38.894 8221 8267 W PathParser: Points are too far apart 4.013175471457885 11-19 14:08:38.895 8221 8267 W PathParser: Points are too far apart 4.013175471457856 11-19 14:08:38.896 8221 8267 W PathParser: Points are too far apart 4.013175471457856 11-19 14:08:38.898 8221 8267 W PathParser: Points are too far apart 4.013175471457874 11-19 14:08:38.898 8221 8267 W PathParser: Points are too far apart 4.013175471457874 11-19 14:08:38.899 8221 8267 W PathParser: Points are too far apart 4.0131754714578705 11-19 14:08:38.899 8221 8267 W PathParser: Points are too far apart 4.0131754714578705 11-19 14:08:38.900 8221 8267 W PathParser: Points are too far apart 4.0131682739187395 11-19 14:08:38.900 8221 8267 W PathParser: Points are too far apart 4.0131682739187395 11-19 14:08:38.900 8221 8267 W PathParser: Points are too far apart 4.013171872685048 11-19 14:08:38.900 8221 8267 W PathParser: Points are too far apart 4.013171872685048 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.013165625763849 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.013171872685043 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.013171872685062 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.013171872685062 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.013171872685023 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.013171872685023 11-19 14:08:38.901 8221 8267 W PathParser: Points are too far apart 4.01317187268506 11-19 14:08:38.902 8221 8267 W PathParser: Points are too far apart 4.01317187268506 11-19 14:08:38.902 8221 8267 W PathParser: Points are too far apart 4.013175471457879 11-19 14:08:38.902 8221 8267 W PathParser: Points are too far apart 4.013175471457879 11-19 14:08:38.902 8221 8267 W PathParser: Points are too far apart 4.01317547145786 11-19 14:08:38.902 8221 8267 W PathParser: Points are too far apart 4.01317547145786 11-19 14:08:38.902 8221 8267 W PathParser: Points are too far apart 4.013175471457859 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.013175471457859 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.01317547145785 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.01317547145785 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.013171872685054 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.013171872685054 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.031698204823579 11-19 14:08:38.903 8221 8267 W PathParser: Points are too far apart 4.031694297728967 11-19 14:08:38.904 8221 8267 W PathParser: Points are too far apart 4.031694297728961 11-19 14:08:38.904 8221 8267 W PathParser: Points are too far apart 4.031694297728961 11-19 14:08:38.904 8221 8267 W PathParser: Points are too far apart 4.031694297728974 11-19 14:08:38.905 8221 8267 W PathParser: Points are too far apart 4.031694297728974 11-19 14:08:38.905 8221 8267 W PathParser: Points are too far apart 4.031694297728961 11-19 14:08:38.905 8221 8267 W PathParser: Points are too far apart 4.031694297728961 11-19 14:08:38.906 8221 8267 W PathParser: Points are too far apart 4.031696251275958 11-19 14:08:38.906 8221 8267 W PathParser: Points are too far apart 4.031696251275958 11-19 14:08:38.906 8221 8267 W PathParser: Points are too far apart 4.031694297728986 11-19 14:08:38.906 8221 8267 W PathParser: Points are too far apart 4.031694297728986 11-19 14:08:38.907 8221 8267 W PathParser: Points are too far apart 4.031693736743918 11-19 14:08:38.907 8221 8267 W PathParser: Points are too far apart 4.031693175759042 11-19 14:08:38.907 8221 8267 W PathParser: Points are too far apart 4.031693736743948 11-19 14:08:38.907 8221 8267 W PathParser: Points are too far apart 4.0316931757590675 11-19 14:08:38.907 8221 8267 W PathParser: Points are too far apart 4.031698204823598 11-19 14:08:38.907 8221 8267 W PathParser: Points are too far apart 4.031694297728991 11-19 14:08:38.969 8221 8267 W PathParser: Points are too far apart 4.013171872685053 11-19 14:08:38.969 8221 8267 W PathParser: Points are too far apart 4.013171872685053 11-19 14:08:38.969 8221 8267 W PathParser: Points are too far apart 4.013171872685072 11-19 14:08:38.970 8221 8267 W PathParser: Points are too far apart 4.013171872685072 11-19 14:08:38.970 8221 8267 W PathParser: Points are too far apart 4.013171872685044 11-19 14:08:38.970 8221 8267 W PathParser: Points are too far apart 4.013171872685044 11-19 14:08:38.971 8221 8267 W PathParser: Points are too far apart 4.013171872685041 11-19 14:08:38.971 8221 8267 W PathParser: Points are too far apart 4.013171872685041 11-19 14:08:38.972 8221 8267 W PathParser: Points are too far apart 4.013171872685054 11-19 14:08:38.972 8221 8267 W PathParser: Points are too far apart 4.013171872685054 11-19 14:08:38.974 8221 8267 W PathParser: Points are too far apart 4.0131718726850485 11-19 14:08:38.974 8221 8267 W PathParser: Points are too far apart 4.0131718726850485 11-19 14:08:38.975 8221 8267 W PathParser: Points are too far apart 4.013175471457856 11-19 14:08:38.975 8221 8267 W PathParser: Points are too far apart 4.013175471457856 11-19 14:08:38.976 8221 8267 W PathParser: Points are too far apart 4.013175471457869 11-19 14:08:38.977 8221 8267 W PathParser: Points are too far apart 4.013175471457869 11-19 14:08:38.977 8221 8267 W PathParser: Points are too far apart 4.01317547145789 11-19 14:08:38.977 8221 8267 W PathParser: Points are too far apart 4.01317547145789 11-19 14:08:38.978 8221 8267 W PathParser: Points are too far apart 4.013175471457873 11-19 14:08:38.978 8221 8267 W PathParser: Points are too far apart 4.013175471457873 11-19 14:08:38.979 8221 8267 W PathParser: Points are too far apart 4.013175471457873 11-19 14:08:38.979 8221 8267 W PathParser: Points are too far apart 4.013175471457873 11-19 14:08:38.979 8221 8267 W PathParser: Points are too far apart 4.013175471457863 11-19 14:08:38.980 8221 8267 W PathParser: Points are too far apart 4.013175471457863 11-19 14:08:38.980 8221 8267 W PathParser: Points are too far apart 4.013175471457874 11-19 14:08:38.980 8221 8267 W PathParser: Points are too far apart 4.013175471457874 11-19 14:08:38.981 8221 8267 W PathParser: Points are too far apart 4.0131682739186605 11-19 14:08:38.981 8221 8267 W PathParser: Points are too far apart 4.0131682739186605 11-19 14:08:38.981 8221 8267 W PathParser: Points are too far apart 4.013171872685045 11-19 14:08:38.982 8221 8267 W PathParser: Points are too far apart 4.013171872685045 11-19 14:08:38.983 8221 8267 W PathParser: Points are too far apart 4.01316562576385 11-19 14:08:38.983 8221 8267 W PathParser: Points are too far apart 4.013171872685049 11-19 14:08:38.983 8221 8267 W PathParser: Points are too far apart 4.0131718726850405 11-19 14:08:38.983 8221 8267 W PathParser: Points are too far apart 4.0131718726850405 11-19 14:08:38.984 8221 8267 W PathParser: Points are too far apart 4.013171872685055 11-19 14:08:38.985 8221 8267 W PathParser: Points are too far apart 4.013171872685055 11-19 14:08:38.986 8221 8267 W PathParser: Points are too far apart 4.0131718726850645 11-19 14:08:38.986 8221 8267 W PathParser: Points are too far apart 4.0131718726850645 11-19 14:08:38.987 8221 8267 W PathParser: Points are too far apart 4.01317547145785 11-19 14:08:38.987 8221 8267 W PathParser: Points are too far apart 4.01317547145785 11-19 14:08:38.987 8221 8267 W PathParser: Points are too far apart 4.013175471457889 11-19 14:08:38.987 8221 8267 W PathParser: Points are too far apart 4.013175471457889 11-19 14:08:38.988 8221 8267 W PathParser: Points are too far apart 4.013175471457867 11-19 14:08:38.988 8221 8267 W PathParser: Points are too far apart 4.013175471457867 11-19 14:08:38.989 8221 8267 W PathParser: Points are too far apart 4.013175471457855 11-19 14:08:38.989 8221 8267 W PathParser: Points are too far apart 4.013175471457855 11-19 14:08:38.989 8221 8267 W PathParser: Points are too far apart 4.013171872685045 11-19 14:08:38.990 8221 8267 W PathParser: Points are too far apart 4.013171872685045 11-19 14:08:38.991 8221 8267 W PathParser: Points are too far apart 4.031698204823581 11-19 14:08:38.991 8221 8267 W PathParser: Points are too far apart 4.031694297728971 11-19 14:08:38.991 8221 8267 W PathParser: Points are too far apart 4.031694297728965 11-19 14:08:38.992 8221 8267 W PathParser: Points are too far apart 4.031694297728965 11-19 14:08:38.992 8221 8267 W PathParser: Points are too far apart 4.031694297728956 11-19 14:08:38.993 8221 8267 W PathParser: Points are too far apart 4.031694297728956 11-19 14:08:38.993 8221 8267 W PathParser: Points are too far apart 4.031694297728964 11-19 14:08:38.993 8221 8267 W PathParser: Points are too far apart 4.031694297728964 11-19 14:08:38.994 8221 8267 W PathParser: Points are too far apart 4.031696251275948 11-19 14:08:38.994 8221 8267 W PathParser: Points are too far apart 4.031696251275948 11-19 14:08:38.995 8221 8267 W PathParser: Points are too far apart 4.0316942977289365 11-19 14:08:38.996 8221 8267 W PathParser: Points are too far apart 4.0316942977289365 11-19 14:08:38.996 8221 8267 W PathParser: Points are too far apart 4.031693736743913 11-19 14:08:38.996 8221 8267 W PathParser: Points are too far apart 4.031693175759052 11-19 14:08:38.997 8221 8267 W PathParser: Points are too far apart 4.031693736743926 11-19 14:08:38.997 8221 8267 W PathParser: Points are too far apart 4.031693175759058 11-19 14:08:38.998 8221 8267 W PathParser: Points are too far apart 4.031694297728965 11-19 14:08:38.998 8221 8267 W PathParser: Points are too far apart 4.031694297728965 11-19 14:08:39.074 8221 8267 W PathParser: Points are too far apart 4.002529609153629 11-19 14:08:39.075 8221 8267 W PathParser: Points are too far apart 4.000008053552097 11-19 14:08:39.075 8221 8267 W PathParser: Points are too far apart 4.004084766022333 11-19 14:08:39.141 1474 3225 W ActivityManager: Unable to start service Intent { cmp=com.miui.daemon/.performance.MiuiPerfService } U=0: not found 11-19 14:08:39.144 8221 8267 W PathParser: Points are too far apart 4.038188644037383 11-19 14:08:39.144 8221 8267 W PathParser: Points are too far apart 4.038188644037383 11-19 14:08:39.145 8221 8267 W PathParser: Points are too far apart 4.038188644037398 11-19 14:08:39.145 8221 8267 W PathParser: Points are too far apart 4.038188644037398 11-19 14:08:39.168 801 801 I MSM-irqbalance: Decided to move IRQ178 from CPU1 to CPU3 11-19 14:08:39.182 8221 8267 W PathParser: Points are too far apart 4.038188644037383 11-19 14:08:39.182 8221 8267 W PathParser: Points are too far apart 4.038188644037383 11-19 14:08:39.183 8221 8267 W PathParser: Points are too far apart 4.038188644037398 11-19 14:08:39.183 8221 8267 W PathParser: Points are too far apart 4.038188644037398 11-19 14:08:39.220 8221 8231 I art : Background partial concurrent mark sweep GC freed 277109(9MB) AllocSpace objects, 11(816KB) LOS objects, 22% free, 54MB/70MB, paused 1.731ms total 264.483ms 11-19 14:08:39.344 8221 8267 W PathParser: Points are too far apart 4.0107891834305285 11-19 14:08:39.344 8221 8267 W PathParser: Points are too far apart 4.0107891834305285 11-19 14:08:39.353 8221 8267 W PathParser: Points are too far apart 4.000168924462442 11-19 14:08:39.367 8221 8267 W PathParser: Points are too far apart 4.000378486894791 11-19 14:08:39.368 8221 8267 W PathParser: Points are too far apart 4.000378486894791 11-19 14:08:39.368 8221 8267 W PathParser: Points are too far apart 4.000374882173244 11-19 14:08:39.368 8221 8267 W PathParser: Points are too far apart 4.000374882173244 11-19 14:08:39.379 8221 8267 W PathParser: Points are too far apart 4.000000773772333 11-19 14:08:39.379 8221 8267 W PathParser: Points are too far apart 4.000000773772333 11-19 14:08:39.381 8221 8267 W PathParser: Points are too far apart 4.000000773772328 11-19 14:08:39.501 8221 8267 V MapImages: Loaded 46 images 11-19 14:08:39.579 8221 8263 I NotesDownload: Downloaded 26 notes in 1.0s 11-19 14:08:39.623 8221 8263 I NoteController: Persisted 21 and deleted 0 notes in 0.0s 11-19 14:08:39.634 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:39.642 8221 8231 I art : Background sticky concurrent mark sweep GC freed 162183(5MB) AllocSpace objects, 4(184KB) LOS objects, 0% free, 69MB/70MB, paused 1.996ms total 183.489ms 11-19 14:08:39.719 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:39.720 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:39.727 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:39.809 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:39.822 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:39.844 8221 8303 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.845 8221 8300 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.847 8221 8298 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.852 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35660/23897.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.854 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/15/17830/11949.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.859 8221 8307 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.864 8221 8304 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.867 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35660/23896.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.868 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35662/23898.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.870 8221 8297 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.872 8221 8231 I art : Background partial concurrent mark sweep GC freed 111719(4MB) AllocSpace objects, 102(15MB) LOS objects, 23% free, 52MB/68MB, paused 2.522ms total 220.927ms 11-19 14:08:39.873 8221 8301 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.877 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35662/23897.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.884 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35661/23896.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.886 8221 8299 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.889 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/15/17831/11948.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.894 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/15/17831/11949.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:39.930 8221 8302 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:39.932 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35662/23896.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:40.000 8221 8305 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:40.002 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35660/23898.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:40.042 8221 8306 V Mbgl-HttpRequest: [HTTP] Request was successful (code = 200). 11-19 14:08:40.047 8221 8254 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/16/35661/23898.pbf?access-token=XQYxWyY9JsVlwq0XYXqB8OO4ttBTNxm46ITHHwPj5F6CX4JaaSMBkvmD8kCqn7z7). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-19 14:08:40.139 8221 8259 I MapTilesDownload: Downloaded 28 tiles (671kB) in 1.4s 11-19 14:08:40.146 8212 8212 I ServiceManager: Waiting for service AtCmdFwd... 11-19 14:08:40.438 8221 8243 I Preloader: Loaded features dictionary in 5.9s 11-19 14:08:40.439 8221 8259 I Preloader: Preloading data took 5.9s 11-19 14:08:40.936 7727 7770 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-19 14:08:41.147 8212 8212 I ServiceManager: Waiting for service AtCmdFwd... 11-19 14:08:42.147 8212 8212 I ServiceManager: Waiting for service AtCmdFwd... 11-19 14:08:42.346 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:42.374 1474 3294 E AppScanObserverService: Result available, null observers for user: 0 11-19 14:08:42.378 4896 4896 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1231 android.content.ContextWrapper.startService:591 android.content.ContextWrapper.startService:591 com.android.settings.MiuiSettingsReceiver.onReceive:115 android.app.ActivityThread.handleReceiver:2805 11-19 14:08:42.547 8221 8263 D OsmAvatarsDownload: Downloaded file 9475258 11-19 14:08:42.553 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:42.644 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:42.657 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:42.873 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.148 8212 8212 I ServiceManager: Waiting for service AtCmdFwd... 11-19 14:08:43.202 8221 8231 I art : Background sticky concurrent mark sweep GC freed 158046(6MB) AllocSpace objects, 8(196KB) LOS objects, 9% free, 61MB/68MB, paused 1.596ms total 109.688ms 11-19 14:08:43.261 8221 8263 D OsmAvatarsDownload: Downloaded file 172435 11-19 14:08:43.267 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.356 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.476 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.572 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.575 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.577 8221 8263 D OsmAvatarsDownload: Downloaded file 9641379 11-19 14:08:43.582 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.602 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] 11-19 14:08:43.664 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:43.666 730 988 W XTCC-5.1.0.13: [CS-RIL-LISTENER] timerCallback fired for ril update registering, re-register 11-19 14:08:43.668 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:43.688 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.777 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.874 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.889 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:43.997 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.049 8221 8231 I art : Background partial concurrent mark sweep GC freed 68814(3MB) AllocSpace objects, 38(4MB) LOS objects, 16% free, 81MB/97MB, paused 1.822ms total 170.326ms 11-19 14:08:44.103 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.104 8221 8263 D OsmAvatarsDownload: Downloaded file 52552 11-19 14:08:44.112 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.149 8212 8212 I ServiceManager: Waiting for service AtCmdFwd... 11-19 14:08:44.166 801 801 I MSM-irqbalance: Decided to move IRQ215 from CPU1 to CPU2 11-19 14:08:44.198 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.306 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.420 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.496 8221 8231 I art : Background sticky concurrent mark sweep GC freed 47050(1821KB) AllocSpace objects, 2(40KB) LOS objects, 2% free, 95MB/97MB, paused 6.471ms total 33.439ms 11-19 14:08:44.527 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.532 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.533 8221 8263 D OsmAvatarsDownload: Downloaded file 1026112 11-19 14:08:44.540 8221 8263 I art : Note: end time exceeds epoch: 11-19 14:08:44.640 8221 8263 I OsmAvatarsDownload: Downloaded 10 avatar images in 5.0s 11-19 14:08:44.695 8221 8259 W PathParser: Points are too far apart 4.000000706425438 11-19 14:08:44.695 8221 8259 W PathParser: Points are too far apart 4.000000706425438 11-19 14:08:44.987 8221 8231 I art : Background partial concurrent mark sweep GC freed 155589(5MB) AllocSpace objects, 6(14MB) LOS objects, 16% free, 82MB/98MB, paused 2.439ms total 206.309ms 11-19 14:08:45.149 8212 8212 W Atfwd_Sendcmd: AtCmdFwd service not published, waiting... retryCnt : 2 11-19 14:08:45.945 7727 7770 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-19 14:08:45.985 8221 8231 I art : Background sticky concurrent mark sweep GC freed 520444(15MB) AllocSpace objects, 0(0B) LOS objects, 15% free, 82MB/98MB, paused 1.831ms total 119.156ms 11-19 14:08:46.977 8221 8231 I art : Background sticky concurrent mark sweep GC freed 547625(15MB) AllocSpace objects, 0(0B) LOS objects, 15% free, 83MB/98MB, paused 5.647ms total 120.746ms 11-19 14:08:47.923 8221 8231 I art : Background sticky concurrent mark sweep GC freed 527001(15MB) AllocSpace objects, 0(0B) LOS objects, 14% free, 84MB/98MB, paused 9.006ms total 120.032ms 11-19 14:08:48.087 3788 3788 I BatteryInfoReceiver: ACTION_BATTERY_CHANGED 11-19 14:08:48.088 3350 3350 D KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED 11-19 14:08:48.089 3350 3350 D KeyguardUpdateMonitor: handleBatteryUpdate 11-19 14:08:48.602 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] 11-19 14:08:48.664 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:48.666 730 988 W XTCC-5.1.0.13: [CS-RIL-LISTENER] timerCallback fired for ril update registering, re-register 11-19 14:08:48.667 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:48.891 8221 8243 W PathParser: Points are too far apart 4.000000706425438 11-19 14:08:48.892 8221 8243 W PathParser: Points are too far apart 4.000000706425438 11-19 14:08:48.895 8221 8243 V MapImages: Loaded 1 images 11-19 14:08:48.919 8221 8231 I art : Background sticky concurrent mark sweep GC freed 481552(14MB) AllocSpace objects, 0(0B) LOS objects, 11% free, 87MB/98MB, paused 1.534ms total 145.920ms 11-19 14:08:49.163 801 801 I MSM-irqbalance: Decided to move IRQ200 from CPU1 to CPU2 11-19 14:08:49.963 8221 8231 I art : Background sticky concurrent mark sweep GC freed 366730(11MB) AllocSpace objects, 2(360KB) LOS objects, 11% free, 87MB/98MB, paused 2.753ms total 156.595ms 11-19 14:08:50.946 7727 7770 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-19 14:08:51.592 8221 8260 I MapDataDownload: Downloaded 14129 nodes, 2471 ways and 35 relations in 13.0s 11-19 14:08:52.442 8221 8231 I art : Background sticky concurrent mark sweep GC freed 188581(5MB) AllocSpace objects, 34(2MB) LOS objects, 7% free, 90MB/98MB, paused 2.086ms total 101.993ms 11-19 14:08:53.251 8221 8231 I art : Background partial concurrent mark sweep GC freed 314480(9MB) AllocSpace objects, 10(20MB) LOS objects, 18% free, 70MB/86MB, paused 1.689ms total 316.736ms 11-19 14:08:53.602 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] 11-19 14:08:53.665 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:53.667 730 988 W XTCC-5.1.0.13: [CS-RIL-LISTENER] timerCallback fired for ril update registering, re-register 11-19 14:08:53.667 639 724 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-19 14:08:54.166 801 801 I MSM-irqbalance: Decided to move IRQ155 from CPU1 to CPU2 11-19 14:08:54.933 8221 8279 F OpenGLRenderer: Error: Spot pair overflow!!! used 195, total 112 11-19 14:08:54.933 8221 8279 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8279 (hwuiTask1) 11-19 14:08:55.036 599 599 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-19 14:08:55.036 599 599 F DEBUG : Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V10.2.1.0.MHOMIXM:user/release-keys' 11-19 14:08:55.036 599 599 F DEBUG : Revision: '0' 11-19 14:08:55.036 599 599 F DEBUG : ABI: 'arm64' 11-19 14:08:55.037 599 599 F DEBUG : pid: 8221, tid: 8279, name: hwuiTask1 >>> de.westnordost.streetcomplete.debug <<< 11-19 14:08:55.037 599 599 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 11-19 14:08:55.094 599 599 F DEBUG : Abort message: 'Error: Spot pair overflow!!! used 195, total 112' 11-19 14:08:55.095 599 599 F DEBUG : x0 0000000000000000 x1 0000000000002057 x2 0000000000000006 x3 0000000000000000 11-19 14:08:55.095 599 599 F DEBUG : x4 0000000000000000 x5 0000000000000001 x6 0000000000000000 x7 0000000000000000 11-19 14:08:55.095 599 599 F DEBUG : x8 0000000000000083 x9 0000007fa9e3e012 x10 0000000000000000 x11 0000007fa9e3d000 11-19 14:08:55.095 599 599 F DEBUG : x12 0000007fa9e28090 x13 0000000000000000 x14 0000007fa9e3d000 x15 0000007fa9e28158 11-19 14:08:55.095 599 599 F DEBUG : x16 0000007facf4a6a8 x17 0000007facf0cbdc x18 0000007fa9e3d000 x19 0000007f80485510 11-19 14:08:55.095 599 599 F DEBUG : x20 0000007f80485450 x21 0000000000000000 x22 0000000000000006 x23 00000000000000c3 11-19 14:08:55.096 599 599 F DEBUG : x24 000000000000001b x25 00000000000000c3 x26 0000005575ed6d10 x27 0000007f80484290 11-19 14:08:55.096 599 599 F DEBUG : x28 00000000000000c3 x29 0000007f80483560 x30 0000007facf0a378 11-19 14:08:55.096 599 599 F DEBUG : sp 0000007f80483560 pc 0000007facf0cbe4 pstate 0000000020000000 11-19 14:08:55.099 599 599 F DEBUG : 11-19 14:08:55.099 599 599 F DEBUG : backtrace: 11-19 14:08:55.099 599 599 F DEBUG : #00 pc 000000000006abe4 /system/lib64/libc.so (tgkill+8) 11-19 14:08:55.099 599 599 F DEBUG : #01 pc 0000000000068374 /system/lib64/libc.so (pthread_kill+68) 11-19 14:08:55.100 599 599 F DEBUG : #02 pc 00000000000212f8 /system/lib64/libc.so (raise+28) 11-19 14:08:55.100 599 599 F DEBUG : #03 pc 000000000001ba98 /system/lib64/libc.so (abort+60) 11-19 14:08:55.100 599 599 F DEBUG : #04 pc 000000000000d328 /system/lib64/libcutils.so (__android_log_assert+236) 11-19 14:08:55.100 599 599 F DEBUG : #05 pc 000000000006f168 /system/lib64/libhwui.so 11-19 14:08:55.100 599 599 F DEBUG : #06 pc 0000000000074d14 /system/lib64/libhwui.so 11-19 14:08:55.100 599 599 F DEBUG : #07 pc 000000150000008b 11-19 14:08:55.149 8212 8212 I ServiceManager: Waiting for service AtCmdFwd... ```

Git bisect log: 6001-bisectlog1.txt

I will try digging some more, and try to comment out some things (if I can figure out which ones) ...

If anybody has any more hints on what to try, let me know.

westnordost commented 1 week ago

👍

You could add a log to onNewIntent, too, because this is most of what changed in the commits you mentioned.

Also, what changed is the version of compose. Maybe compose has a bug. You could try to downgrade Compose to see if the issue also appears for an older version of compose.

mnalis commented 1 week ago

I've tried reverting to previous compose versions used in working 59.3, but it did not help.

It seems it crashes even if it never got data from the Internet, and that it crashes only when current location pointer gets off the screen. Below are the detailed steps, logs, and video. Any hint what to try next?

Here is the log and the video: crash_left_20241120_1930.txt

https://github.com/user-attachments/assets/14967a73-8b3e-418a-ac42-6af25b1f7bbc

westnordost commented 1 week ago

Okay, we are getting closer. In MainScreen, in line 372 or so, the PointerPinButton is added.

What I find interesting, is that in your video, the display of that button flickers. What is happening here? Is the calculated intersection alternating between null and a proper value? You could log that to see what the values are.

Also, if the crash never happens when it is at the top of the screen, maybe it has something to do with positioning the pointer pin button? You could replace the Modifier with modifier = Modifier.align(Alignment.Center), to make it always display at the center of the screen. Is the crash still reproducible, then?

mnalis commented 1 week ago

BTW, I've noticed following in the log, which seems related to StreetComplete debug build: 

11-21 00:50:13.060 27806 27806 E Mbgl    : {tcomplete.debug}[JNI]: Error setting property: symbol-sort-key layer doesn't support this property
11-21 00:50:13.060 27806 27806 E Mbgl    : {tcomplete.debug}[JNI]: Error setting property: icon-allow-overlap layer doesn't support this property
11-21 00:50:13.060 27806 27806 E Mbgl    : {tcomplete.debug}[JNI]: Error setting property: icon-ignore-placement layer doesn't support this property

Is that perhaps interesting?

What I find interesting, is that in your video, the display of that button flickers. What is happening here? Is the calculated intersection alternating between null and a proper value? You could log that to see what the values are.

I've addeded that debug and it displays the following when pointers go up and flickers:

The values in the log look normal to me: ``` 11-21 00:51:06.373 27806 27894 I Mbgl-HttpRequest: Request failed due to a connection error: Unable to resolve host "tile.jawg.io": No address associated with hostname 11-21 00:51:06.374 27806 27837 D Mbgl-HttpRequest: [HTTP] This request was cancelled (https://tile.jawg.io/streets-v2+hillshade-v1/0/0/0.pbf?access-token=mL9X4SwxfsAGfojvGiion9hPKuGLKxPbogLyMbtakA2gJ3X88gcVlTSQ7OD6OfbZ). This is expected for tiles that were being prefetched but are no longer needed for the map to render. 11-21 00:51:06.385 27806 27855 E Mbgl : {RenderThread 60}[Style]: Failed to load tile 0/0/0=>0 for source jawg-streets: Unable to resolve host "tile.jawg.io": No address associated with hostname 11-21 00:51:08.962 27514 27570 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-21 00:51:12.814 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.69345796 xDp=176.27203.dp yDp=24.0.dp 11-21 00:51:12.880 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.69035023 xDp=176.28876.dp yDp=24.0.dp 11-21 00:51:12.905 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6876796 xDp=176.30315.dp yDp=24.0.dp 11-21 00:51:12.929 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.686375 xDp=176.31017.dp yDp=24.0.dp 11-21 00:51:12.948 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6843055 xDp=176.32124.dp yDp=24.0.dp 11-21 00:51:12.970 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6824545 xDp=176.33122.dp yDp=24.0.dp 11-21 00:51:13.001 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6801527 xDp=176.34358.dp yDp=24.0.dp 11-21 00:51:13.021 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5577421 xDp=177.00171.dp yDp=24.0.dp 11-21 00:51:13.033 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5572093 xDp=177.00458.dp yDp=24.0.dp 11-21 00:51:13.043 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.55667657 xDp=177.00743.dp yDp=24.0.dp 11-21 00:51:13.060 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5561438 xDp=177.0103.dp yDp=24.0.dp 11-21 00:51:13.076 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5555974 xDp=177.01324.dp yDp=24.0.dp 11-21 00:51:13.095 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5550715 xDp=177.01607.dp yDp=24.0.dp 11-21 00:51:13.131 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5533639 xDp=177.02525.dp yDp=24.0.dp 11-21 00:51:13.176 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.49000028 xDp=177.36589.dp yDp=24.0.dp 11-21 00:51:13.194 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.4896178 xDp=177.36797.dp yDp=24.0.dp 11-21 00:51:13.209 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.48860008 xDp=177.3734.dp yDp=24.0.dp 11-21 00:51:13.260 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.48793072 xDp=177.37701.dp yDp=24.0.dp 11-21 00:51:13.277 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.48764387 xDp=177.37856.dp yDp=24.0.dp 11-21 00:51:13.309 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.48713842 xDp=177.38127.dp yDp=24.0.dp 11-21 00:51:13.343 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.48612756 xDp=177.3867.dp yDp=24.0.dp 11-21 00:51:13.577 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5453726 xDp=177.06822.dp yDp=24.0.dp 11-21 00:51:13.618 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.666991 xDp=176.41435.dp yDp=24.0.dp 11-21 00:51:13.660 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.6825582 xDp=170.95262.dp yDp=24.0.dp 11-21 00:51:13.677 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.978722 xDp=169.3589.dp yDp=24.0.dp 11-21 00:51:13.693 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.2580085 xDp=167.85551.dp yDp=24.0.dp 11-21 00:51:13.711 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.4843063 xDp=166.63696.dp yDp=24.0.dp 11-21 00:51:13.737 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.7371325 xDp=165.27501.dp yDp=24.0.dp 11-21 00:51:13.760 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-3.0164325 xDp=163.76982.dp yDp=24.0.dp 11-21 00:51:13.777 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-3.085356 xDp=163.39827.dp yDp=24.0.dp 11-21 00:51:13.794 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-3.144321 xDp=163.08034.dp yDp=24.0.dp 11-21 00:51:13.809 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-3.1785266 xDp=162.89594.dp yDp=24.0.dp 11-21 00:51:13.972 27514 27570 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-21 00:51:13.994 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-3.1411178 xDp=163.09763.dp yDp=24.0.dp 11-21 00:51:14.038 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-3.1331196 xDp=163.14075.dp yDp=24.0.dp 11-21 00:51:14.095 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.5966902 xDp=166.03162.dp yDp=24.0.dp 11-21 00:51:14.116 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.4186819 xDp=166.99037.dp yDp=24.0.dp 11-21 00:51:14.158 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.2522097 xDp=167.88676.dp yDp=24.0.dp 11-21 00:51:14.185 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-2.1652272 xDp=168.35504.dp yDp=24.0.dp 11-21 00:51:14.196 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.9801426 xDp=169.35127.dp yDp=24.0.dp 11-21 00:51:14.209 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.9747536 xDp=169.3803.dp yDp=24.0.dp 11-21 00:51:14.227 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.9135551 xDp=169.70964.dp yDp=24.0.dp 11-21 00:51:14.243 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.9100854 xDp=169.72833.dp yDp=24.0.dp 11-21 00:51:14.279 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.9076129 xDp=169.74162.dp yDp=24.0.dp 11-21 00:51:14.307 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.8471862 xDp=170.06679.dp yDp=24.0.dp 11-21 00:51:14.326 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.7269953 xDp=170.71352.dp yDp=24.0.dp 11-21 00:51:14.343 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.6819093 xDp=170.9561.dp yDp=24.0.dp 11-21 00:51:14.361 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.6422396 xDp=171.16954.dp yDp=24.0.dp 11-21 00:51:14.391 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.665305 xDp=171.04543.dp yDp=24.0.dp 11-21 00:51:14.426 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.5445678 xDp=171.69499.dp yDp=24.0.dp 11-21 00:51:14.443 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.457517 xDp=172.16327.dp yDp=24.0.dp 11-21 00:51:14.460 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.4261938 xDp=172.33174.dp yDp=24.0.dp 11-21 00:51:14.477 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.3646743 xDp=172.66264.dp yDp=24.0.dp 11-21 00:51:14.510 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.3109275 xDp=172.95172.dp yDp=24.0.dp 11-21 00:51:14.533 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.2112683 xDp=173.48772.dp yDp=24.0.dp 11-21 00:51:14.561 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.0576026 xDp=174.31407.dp yDp=24.0.dp 11-21 00:51:14.577 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-1.0143812 xDp=174.54651.dp yDp=24.0.dp 11-21 00:51:14.595 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.95599675 xDp=174.86046.dp yDp=24.0.dp 11-21 00:51:14.603 14616 14916 W ActivityManager: Unable to start service Intent { cmp=com.miui.daemon/.performance.MiuiPerfService } U=0: not found 11-21 00:51:14.629 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.8988486 xDp=175.16774.dp yDp=24.0.dp 11-21 00:51:14.658 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.7843951 xDp=175.78314.dp yDp=24.0.dp 11-21 00:51:14.676 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.7273357 xDp=176.0899.dp yDp=24.0.dp 11-21 00:51:14.694 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.7273357 xDp=176.0899.dp yDp=24.0.dp 11-21 00:51:14.726 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6441645 xDp=176.53706.dp yDp=24.0.dp 11-21 00:51:14.776 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6710276 xDp=176.39264.dp yDp=24.0.dp 11-21 00:51:14.793 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6703924 xDp=176.39607.dp yDp=24.0.dp 11-21 00:51:15.077 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.66910833 xDp=176.40297.dp yDp=24.0.dp 11-21 00:51:15.144 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.66846627 xDp=176.40642.dp yDp=24.0.dp 11-21 00:51:15.194 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6131213 xDp=176.70398.dp yDp=24.0.dp 11-21 00:51:15.236 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.61253387 xDp=176.70714.dp yDp=24.0.dp 11-21 00:51:15.294 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.6113659 xDp=176.7134.dp yDp=24.0.dp 11-21 00:51:15.326 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.50167304 xDp=177.30315.dp yDp=24.0.dp 11-21 00:51:15.377 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.5013042 xDp=177.30511.dp yDp=24.000021.dp 11-21 00:51:15.412 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.46635416 xDp=177.49303.dp yDp=24.0.dp 11-21 00:51:15.431 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.41922584 xDp=177.74635.dp yDp=24.0.dp 11-21 00:51:15.481 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.44558355 xDp=177.60468.dp yDp=24.0.dp 11-21 00:51:15.526 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.39035463 xDp=177.90157.dp yDp=24.0.dp 11-21 00:51:15.544 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.39035463 xDp=177.90157.dp yDp=24.0.dp 11-21 00:51:15.560 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.39017022 xDp=177.90254.dp yDp=24.0.dp ```

however, it seems that it flickers because on some movements it doesn't get drawn, even if values look normal, e.g. here:

11-21 00:51:15.610 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.38943258 xDp=177.90651.dp yDp=24.0.dp
11-21 00:51:15.644 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.32861656 xDp=178.23344.dp yDp=24.0.dp

<!-- the icon wasn't displayed at all here, and I stopped touching the screen 
for dozen seconds and it still wasn't displayed. 
When I then started panning again below, the icon appeared again and continued flickering as I panned -->

11-21 00:51:18.982 27514 27570 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext
11-21 00:51:23.995 27514 27570 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext
11-21 00:51:24.029 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.32877365 xDp=178.23262.dp yDp=24.0.dp
11-21 00:51:24.069 27806 27806 E POINTERPIN: Creating PointerPinButton rotate=-0.32906052 xDp=178.2311.dp yDp=24.0.dp

Values leading to the crash also look normal if I pan the screen so icon goes off on the left edge of the screen:

11-21 01:06:05.244 28251 28251 E POINTERPIN: Creating PointerPinButton rotate=263.64233 xDp=0.0.dp yDp=352.05554.dp
11-21 01:06:05.325 28251 28251 E POINTERPIN: Creating PointerPinButton rotate=263.4318 xDp=0.0.dp yDp=352.72546.dp
11-21 01:06:05.358 28251 28251 E POINTERPIN: Creating PointerPinButton rotate=263.42114 xDp=0.0.dp yDp=352.7594.dp
11-21 01:06:05.372 28251 28308 F OpenGLRenderer: Error: Spot pair overflow!!! used 186, total 116
11-21 01:06:05.372 28251 28308 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 28308 (hwuiTask1)
11-21 01:06:05.392 28251 28251 E POINTERPIN: Creating PointerPinButton rotate=263.35764 xDp=0.0.dp yDp=352.96158.dp
11-21 01:06:05.479   599   599 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-21 01:06:05.479   599   599 F DEBUG   : Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V10.2.1.0.MHOMIXM:user/release-keys'
11-21 01:06:05.480   599   599 F DEBUG   : Revision: '0'
11-21 01:06:05.480   599   599 F DEBUG   : ABI: 'arm64'
11-21 01:06:05.481   599   599 F DEBUG   : pid: 28251, tid: 28308, name: hwuiTask1  >>> de.westnordost.streetcomplete.debug <<<
11-21 01:06:05.481   599   599 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
mnalis commented 1 week ago

You could replace the Modifier with modifier = Modifier.align(Alignment.Center), to make it always display at the center of the screen. Is the crash still reproducible, then?

Yes. In fact, with that change, it now crashes even if it goes to the top of the screen:

11-21 01:17:12.031 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=4.4195194 xDp=203.80486.dp yDp=24.0.dp
11-21 01:17:12.077 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=4.737622 xDp=205.52582.dp yDp=24.0.dp
11-21 01:17:12.093 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=4.800473 xDp=205.86604.dp yDp=24.0.dp
11-21 01:17:12.111 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=4.8631606 xDp=206.20543.dp yDp=24.0.dp
11-21 01:17:12.129 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=4.9864388 xDp=206.87305.dp yDp=24.0.dp
11-21 01:17:12.145 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=5.01031 xDp=207.00238.dp yDp=24.0.dp
11-21 01:17:12.152 29583 29638 F OpenGLRenderer: Error: Spot pair overflow!!! used 206, total 112
--------- beginning of crash
11-21 01:17:12.152 29583 29638 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 29638 (hwuiTask1)
11-21 01:17:12.161 29583 29583 E POINTERPIN: Creating PointerPinButton rotate=5.0433683 xDp=207.18146.dp yDp=24.0.dp
11-21 01:17:12.255   599   599 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-21 01:17:12.256   599   599 F DEBUG   : Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V10.2.1.0.MHOMIXM:user/release-keys'
11-21 01:17:12.256   599   599 F DEBUG   : Revision: '0'
11-21 01:17:12.256   599   599 F DEBUG   : ABI: 'arm64'
11-21 01:17:12.256   599   599 F DEBUG   : pid: 29583, tid: 29638, name: hwuiTask1  >>> de.westnordost.streetcomplete.debug <<<
11-21 01:17:12.256   599   599 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-21 01:17:12.295   599   599 F DEBUG   : Abort message: 'Error: Spot pair overflow!!! used 206, total 112'
11-21 01:17:12.295   599   599 F DEBUG   :     x0   0000000000000000  x1   00000000000073c6  x2   0000000000000006  x3   0000000000000000
11-21 01:17:12.296   599   599 F DEBUG   :     x4   0000000000000000  x5   0000000000000001  x6   0000000000000000  x7   0000000000000000
11-21 01:17:12.296   599   599 F DEBUG   :     x8   0000000000000083  x9   0000007f88f10012  x10  0000000000000000  x11  0000007f88f0f000
11-21 01:17:12.296   599   599 F DEBUG   :     x12  0000007f88efa090  x13  0000000000000000  x14  0000007f88f0f000  x15  0000007f88efa158
11-21 01:17:12.296   599   599 F DEBUG   :     x16  0000007f8c01c6a8  x17  0000007f8bfdebdc  x18  0000007f88f0f000  x19  0000007f5f53f510
11-21 01:17:12.296   599   599 F DEBUG   :     x20  0000007f5f53f450  x21  0000000000000000  x22  0000000000000006  x23  00000000000000ce
11-21 01:17:12.296   599   599 F DEBUG   :     x24  000000000000001b  x25  00000000000000ce  x26  00000055a64e9a40  x27  0000007f5f53e290
11-21 01:17:12.297   599   599 F DEBUG   :     x28  00000000000000ce  x29  0000007f5f53d560  x30  0000007f8bfdc378
11-21 01:17:12.297   599   599 F DEBUG   :     sp   0000007f5f53d560  pc   0000007f8bfdebe4  pstate 0000000020000000
11-21 01:17:12.300   599   599 F DEBUG   :
11-21 01:17:12.300   599   599 F DEBUG   : backtrace:
11-21 01:17:12.301   599   599 F DEBUG   :     #00 pc 000000000006abe4  /system/lib64/libc.so (tgkill+8)
11-21 01:17:12.301   599   599 F DEBUG   :     #01 pc 0000000000068374  /system/lib64/libc.so (pthread_kill+68)
11-21 01:17:12.301   599   599 F DEBUG   :     #02 pc 00000000000212f8  /system/lib64/libc.so (raise+28)
11-21 01:17:12.301   599   599 F DEBUG   :     #03 pc 000000000001ba98  /system/lib64/libc.so (abort+60)
11-21 01:17:12.301   599   599 F DEBUG   :     #04 pc 000000000000d328  /system/lib64/libcutils.so (__android_log_assert+236)
11-21 01:17:12.301   599   599 F DEBUG   :     #05 pc 000000000006f168  /system/lib64/libhwui.so
11-21 01:17:12.301   599   599 F DEBUG   :     #06 pc 0000000000074d14  /system/lib64/libhwui.so
11-21 01:17:12.302   599   599 F DEBUG   :     #07 pc 000000030000008b  <unknown>
11-21 01:17:12.915 14616 29661 W ActivityManager:   Force finishing activity de.westnordost.streetcomplete.debug/de.westnordost.streetcomplete.screens.main.MainActivity
westnordost commented 1 week ago

Is that perhaps interesting?

No.

intersection logs / flickering

Okay, interesting. So, the calculation is fine, and the calculation isn't "flickering". But for some reason, it's not drawn every second-or-so UI update. That'd be an issue on its own, but maybe it is connected.

Yes. In fact, with that change, it now crashes even if it goes to the top of the screen:

What do you mean? It shouldn't go to the top of the screen but be in the center of the screen always.

mnalis commented 6 days ago

What do you mean? It shouldn't go to the top of the screen but be in the center of the screen always.

Yeah, that extra pointer which points towards the current location (blue dot in white teardrop) is indeed pinned in the center of the screen instead pinned to one of the borders (as it was before), but when the original location icon (blue circle with direction-view-cone) goes on the top of the screen, it crashes (while location icon going up was only survivable direction before this centering-change)

Here is a video, perhaps it will be clearer:

https://github.com/user-attachments/assets/84c76433-8843-4ad0-83b6-807a8bc0ba77

westnordost commented 4 days ago

Weird, how can it crash now when less things are done? (I.e. no positioning is done)

Regarding the flickering, you put the log at the position where intersection is already known to not be null. So does that mean that every second or so time, intersection is null? (If yes, we should get to the bottom of this. Why is no intersection found?)

mnalis commented 1 day ago

Weird, how can it crash now when less things are done? (I.e. no positioning is done)

I have no idea :man_shrugging:

However, when I remove PointerPinButton call completely (https://github.com/mnalis/StreetComplete/commit/6915963c233a9cc135145745c5b48ade786c75a7) then the app seems to work just fine:

log_SC_removed_PointerPinButton-6915963.txt

https://github.com/user-attachments/assets/9d604c54-4835-470a-86e1-5481836e5966

Any other ideas what I could try?

Regarding the flickering, you put the log at the position where intersection is already known to not be null. So does that mean that every second or so time, intersection is null? (If yes, we should get to the bottom of this. Why is no intersection found?)

I'm totally out of my depth here (as I don't even understand how those things get called and by who) so can't even say if your question is rhetorical question or am I supposed to try something here to provide the answer, sorry. :sweat_smile:

I'm willing to try any idea you have and test and provide output, but I have no idea how/where to add debug points...

mnalis commented 1 day ago

However, when I remove PointerPinButton call completely (https://github.com/mnalis/StreetComplete/commit/6915963c233a9cc135145745c5b48ade786c75a7) then the app seems to work just fine

I've managed to find another datapoint: it doesn't crash if I leave PointerPinButton call in, but force rotate=0.0f or rotate=45.0f (instead of original rotation.toFloat()) -- regardless of whether I use modifier.absoluteOffset or modifier.align(Alignment.Center) !

mnalis commented 1 day ago

Ok, this is getting more and more bizzare. I've done three tests, all the same with PointerPinButton in the center, but instead of using actual angle, they had different rotation value hardcoded (that was the only variable changed between them). Those tests resulted in 3 different behaviours:

westnordost commented 1 day ago

Okay, let's try two things. First, revert to the current master state, then add

1.

Log.d("MNALIS", intersection?.let { "a=${it.angle}, x=${it.position.x}, y=${it.position.x}" } ?: "null")

just before

intersection?.let { (offset, angle) ->

(you need to add import de.westnordost.streetcomplete.util.logs.Log at the top)

The log output, does it log "null" often/sometimes? Or always an angle plus position?

  1. So, apparently the crash happens due to the rotation of the widget. If you just set the rotation to something constant, e.g. 0, then everything else works?
westnordost commented 1 day ago

Do you have Android Studio installed?

  1. also, starting from master, remove line 67 and line 57 in PointerPinButton.kt (the stuff with the shape). Does this solve the crash?

  2. starting from master, remove lines 61-65 in PointerPinButton.kt. Does this solve the crash?

mnalis commented 1 day ago
  1. Log.d("MNALIS", intersection?.let { "a=${it.angle}, x=${it.position.x}, y=${it.position.x}" } ?: "null") The log output, does it log "null" often/sometimes? Or always an angle plus position?

OK, done in https://github.com/mnalis/StreetComplete/commit/c77c47cea60a65356914f60809c4bf2680c5c163. It seems to display "null" very often, but it seems to me only while my location is still inside of the screen. When I get out of the screen so teardrop-pin is created, it seems to only contain positive values until it crashes, e.g.

example log ``` 11-28 22:02:23.262 16663 16663 D MNALIS : null 11-28 22:02:23.278 16663 16663 D MNALIS : null 11-28 22:02:23.295 16663 16663 D MNALIS : null 11-28 22:02:23.312 16663 16663 D MNALIS : null 11-28 22:02:23.329 16663 16663 D MNALIS : null 11-28 22:02:23.345 16663 16663 D MNALIS : null 11-28 22:02:23.362 16663 16663 D MNALIS : null 11-28 22:02:23.379 16663 16663 D MNALIS : null 11-28 22:02:23.395 16663 16663 D MNALIS : null 11-28 22:02:23.412 16663 16663 D MNALIS : null 11-28 22:02:23.428 16663 16663 D MNALIS : null 11-28 22:02:23.445 16663 16663 D MNALIS : null 11-28 22:02:23.462 16663 16663 D MNALIS : null 11-28 22:02:23.478 16663 16663 D MNALIS : null 11-28 22:02:23.512 16663 16663 D MNALIS : null 11-28 22:02:23.546 16663 16663 D MNALIS : null 11-28 22:02:23.564 16663 16663 D MNALIS : null 11-28 22:02:23.579 16663 16663 D MNALIS : null 11-28 22:02:23.595 16663 16663 D MNALIS : null 11-28 22:02:23.612 16663 16663 D MNALIS : null 11-28 22:02:23.629 16663 16663 D MNALIS : null 11-28 22:02:23.646 16663 16663 D MNALIS : null 11-28 22:02:23.663 16663 16663 D MNALIS : null 11-28 22:02:23.679 16663 16663 D MNALIS : null 11-28 22:02:23.695 16663 16663 D MNALIS : null 11-28 22:02:23.713 16663 16663 D MNALIS : null 11-28 22:02:23.730 16663 16663 D MNALIS : null 11-28 22:02:23.745 16663 16663 D MNALIS : null 11-28 22:02:23.762 16663 16663 D MNALIS : null 11-28 22:02:23.778 16663 16663 D MNALIS : null 11-28 22:02:23.795 16663 16663 D MNALIS : null 11-28 22:02:23.812 16663 16663 D MNALIS : null 11-28 22:02:23.829 16663 16663 D MNALIS : null 11-28 22:02:23.846 16663 16663 D MNALIS : null 11-28 22:02:23.862 16663 16663 D MNALIS : null 11-28 22:02:23.879 16663 16663 D MNALIS : null 11-28 22:02:23.896 16663 16663 D MNALIS : null 11-28 22:02:23.913 16663 16663 D MNALIS : null 11-28 22:02:23.931 16663 16663 D MNALIS : null 11-28 22:02:23.945 16663 16663 D MNALIS : null 11-28 22:02:23.962 16663 16663 D MNALIS : null 11-28 22:02:23.978 16663 16663 D MNALIS : null 11-28 22:02:23.994 16663 16663 D MNALIS : null 11-28 22:02:24.028 16663 16663 D MNALIS : null 11-28 22:02:24.062 16663 16663 D MNALIS : null 11-28 22:02:24.094 16663 16663 D MNALIS : null 11-28 22:02:24.128 16663 16663 D MNALIS : null 11-28 22:02:24.195 16663 16663 D MNALIS : null 11-28 22:02:24.372 16157 16157 I ServiceManager: Waiting for service AtCmdFwd... 11-28 22:02:25.062 15512 15554 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-28 22:02:25.372 16157 16157 I ServiceManager: Waiting for service AtCmdFwd... 11-28 22:02:26.028 646 682 E QCALOG : [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] 11-28 22:02:26.077 646 682 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-28 22:02:26.369 695 909 W XTCC-5.1.0.13: [CS-RIL-LISTENER] timerCallback fired for ril update registering, re-register 11-28 22:02:26.369 646 682 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-28 22:02:26.373 16157 16157 I ServiceManager: Waiting for service AtCmdFwd... 11-28 22:02:27.373 16157 16157 I ServiceManager: Waiting for service AtCmdFwd... 11-28 22:02:27.914 850 850 I MSM-irqbalance: Decided to move IRQ222 from CPU3 to CPU0 11-28 22:02:28.374 16157 16157 I ServiceManager: Waiting for service AtCmdFwd... 11-28 22:02:29.374 16157 16157 W Atfwd_Sendcmd: AtCmdFwd service not published, waiting... retryCnt : 5 11-28 22:02:30.069 15512 15554 E chromium: [ERROR:aw_gl_functor.cc(101)] Received unexpected kModeProcessNoContext 11-28 22:02:31.029 646 682 E QCALOG : [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] 11-28 22:02:31.077 646 682 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-28 22:02:31.369 695 909 W XTCC-5.1.0.13: [CS-RIL-LISTENER] timerCallback fired for ril update registering, re-register 11-28 22:02:31.370 646 682 E QCALOG : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] 11-28 22:02:31.447 16663 16663 D MNALIS : null 11-28 22:02:31.464 16663 16663 D MNALIS : null 11-28 22:02:31.480 16663 16663 D MNALIS : null 11-28 22:02:31.498 16663 16663 D MNALIS : a=1.3310025791313986, x=1080.0, y=1080.0 11-28 22:02:31.563 16663 16663 D MNALIS : a=1.3439281145718436, x=1080.0, y=1080.0 11-28 22:02:31.587 16663 16663 D MNALIS : a=1.3457613448288779, x=1080.0, y=1080.0 11-28 22:02:31.604 16663 16663 D MNALIS : a=1.3470176766302924, x=1080.0, y=1080.0 11-28 22:02:31.621 16663 16663 D MNALIS : a=1.3492369512703757, x=1080.0, y=1080.0 11-28 22:02:31.634 16663 16663 D MNALIS : a=1.350427464642797, x=1080.0, y=1080.0 11-28 22:02:31.671 16663 16663 D MNALIS : a=1.3516136119749884, x=1080.0, y=1080.0 11-28 22:02:31.699 16663 16663 D MNALIS : a=1.3522447357561926, x=1080.0, y=1080.0 11-28 22:02:31.813 16663 16663 D MNALIS : a=1.351245061555181, x=1080.0, y=1080.0 11-28 22:02:31.831 16663 16663 D MNALIS : a=1.3491608361389975, x=1080.0, y=1080.0 11-28 22:02:31.862 16663 16663 D MNALIS : a=1.3477531681444983, x=1080.0, y=1080.0 11-28 22:02:31.873 16663 16718 F OpenGLRenderer: Error: Spot pair overflow!!! used 173, total 108 11-28 22:02:31.874 16663 16718 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 16718 (hwuiTask1) 11-28 22:02:31.881 16663 16663 D MNALIS : a=1.3455837527897696, x=1080.0, y=1080.0 11-28 22:02:31.979 609 609 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-28 22:02:31.979 609 609 F DEBUG : Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V10.2.1.0.MHOMIXM:user/release-keys' 11-28 22:02:31.979 609 609 F DEBUG : Revision: '0' 11-28 22:02:31.979 609 609 F DEBUG : ABI: 'arm64' 11-28 22:02:31.979 609 609 F DEBUG : pid: 16663, tid: 16718, name: hwuiTask1 >>> de.westnordost.streetcomplete.debug <<< 11-28 22:02:31.980 609 609 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 11-28 22:02:32.028 609 609 F DEBUG : Abort message: 'Error: Spot pair overflow!!! used 173, total 108' 11-28 22:02:32.028 609 609 F DEBUG : x0 0000000000000000 x1 000000000000414e x2 0000000000000006 x3 0000000000000000 11-28 22:02:32.028 609 609 F DEBUG : x4 0000000000000000 x5 0000000000000001 x6 0000000000000000 x7 0000000000000000 11-28 22:02:32.028 609 609 F DEBUG : x8 0000000000000083 x9 0000007f9f934012 x10 0000000000000000 x11 0000007f9f933000 11-28 22:02:32.028 609 609 F DEBUG : x12 0000007f9f91e090 x13 0000000000000000 x14 0000007f9f933000 x15 0000007f9f91e158 11-28 22:02:32.028 609 609 F DEBUG : x16 0000007fa2a406a8 x17 0000007fa2a02bdc x18 0000007f9f933000 x19 0000007f76043510 11-28 22:02:32.029 609 609 F DEBUG : x20 0000007f76043450 x21 0000000000000000 x22 0000000000000006 x23 00000000000000ad 11-28 22:02:32.029 609 609 F DEBUG : x24 000000000000001b x25 00000000000000ad x26 00000055b7f3e980 x27 0000007f76042290 11-28 22:02:32.029 609 609 F DEBUG : x28 00000000000000ad x29 0000007f760415a0 x30 0000007fa2a00378 11-28 22:02:32.029 609 609 F DEBUG : sp 0000007f760415a0 pc 0000007fa2a02be4 pstate 0000000020000000 11-28 22:02:32.032 609 609 F DEBUG : 11-28 22:02:32.032 609 609 F DEBUG : backtrace: 11-28 22:02:32.032 609 609 F DEBUG : #00 pc 000000000006abe4 /system/lib64/libc.so (tgkill+8) 11-28 22:02:32.032 609 609 F DEBUG : #01 pc 0000000000068374 /system/lib64/libc.so (pthread_kill+68) 11-28 22:02:32.033 609 609 F DEBUG : #02 pc 00000000000212f8 /system/lib64/libc.so (raise+28) 11-28 22:02:32.033 609 609 F DEBUG : #03 pc 000000000001ba98 /system/lib64/libc.so (abort+60) 11-28 22:02:32.033 609 609 F DEBUG : #04 pc 000000000000d328 /system/lib64/libcutils.so (__android_log_assert+236) 11-28 22:02:32.033 609 609 F DEBUG : #05 pc 000000000006f168 /system/lib64/libhwui.so 11-28 22:02:32.033 609 609 F DEBUG : #06 pc 0000000000074d14 /system/lib64/libhwui.so 11-28 22:02:32.033 609 609 F DEBUG : #07 pc 0000000c00000087 1 ```
  1. So, apparently the crash happens due to the rotation of the widget. If you just set the rotation to something constant, e.g. 0, then everything else works?

Depends on the constant, see https://github.com/streetcomplete/StreetComplete/issues/6001#issuecomment-2506709569 for examples. Yes, with 0 (and 45) everything works normally, but constant 75.02551 crashes, and constant 75.0100 doesn't display the pin (but doesn't crash either).

Do you have Android Studio installed?

No.

  1. also, starting from master, remove line 67 and line 57 in PointerPinButton.kt (the stuff with the shape). Does this solve the crash?

Yes, (https://github.com/mnalis/StreetComplete/commit/d98839309e076925a85b0c7e9f660e936106c5ee) solves the crash (the pin is displayed as blue circle in white box)

  1. starting from master, remove lines 61-65 in PointerPinButton.kt. Does this solve the crash?

Yes, (https://github.com/mnalis/StreetComplete/commit/2500c76d769afcf7ca2e9aa9315ef375cc7cafde) also solves the crash (the pin looks normal blue dot in white teardrop and even seems to rotate correctly, but it is always placed at top-left corner no matter which side of the screen I moved the GPS dot out)

westnordost commented 23 hours ago

What, either of 3 and 4 solves the crash? Are you sure?

mnalis commented 21 hours ago

What, either of 3 and 4 solves the crash? Are you sure?

Yes, either of those changes avoids the crash.

Here is video of only change 3 (https://github.com/mnalis/StreetComplete/commit/d98839309e076925a85b0c7e9f660e936106c5ee):

https://github.com/user-attachments/assets/946243d2-0e36-4153-9d9e-22cf23580f4d

And here is video of only change 4 (https://github.com/mnalis/StreetComplete/commit/2500c76d769afcf7ca2e9aa9315ef375cc7cafde):

https://github.com/user-attachments/assets/8354c3c1-1705-434c-b695-1d9776522201

mnalis commented 18 hours ago

Looking at the code and searching the net, I've found a workaround; forcing elevation = 0.dp in PointerPinButton():

https://github.com/mnalis/StreetComplete/commit/b24230f7abefa535b04ec2a46db8754a533c2b39#diff-d8525b7358f4e0685bcc6c4d663ea4fa11fcd9abfe8f849b0aa28239bea47860L70

Doing that fixes the crash, at only the cost of not displaying slight shadow on that teardrop pin.

It seems to be an known issue in some Android versions, see https://stackoverflow.com/a/37249265/2600099

So, shadow can be disabled always there, or only when problematic Android version is detected, like e.g. here: https://github.com/material-components/material-components-android/commit/3c3ac61c9126a7b97da7e10324be163c11257e53

Would you like me to make a PR @westnordost, and if so, which solution would you prefer?

westnordost commented 8 hours ago

Alright, I'll try that, thank you for your relentless testing!

westnordost commented 8 hours ago

Alright, I'll try that, thank you for your relentless testing! Do you have an Android 7 device with which you can reproduce the issue? Otherwise, I will jsut add the exception for Android 6

mnalis commented 6 hours ago

Do you have an Android 7 device with which you can reproduce the issue?

Unfortunately not, only Android 7.1 device I have does not support GLES 3.0 so it doesn't really display anything in recent SC versions (https://github.com/streetcomplete/StreetComplete/issues/6029)... I've tried moving screen around blindly on that device and it didn't seem to crash, but that is more likely because MapLibre doesn't work at all there (as other things looks fishy too), then a confirmation the bug doesn't exist in Android 7... :man_shrugging:

Next device up which I have is Android 9, and that does not have the bug...