Altonss

> Do you have access to your system log? (`adb logcat`) Maybe the system log will reveal what is going wrong. I will try to do `adb logcat` as son...

I managed to record the crash with adb logcat :) Which part is important for you (because it's pretty long, and haven't looked at it if there is any personnal...

``` 08-08 16:27:31.778 22772 22805 F hardened_malloc: fatal allocator error: detected write after free 08-08 16:27:31.778 22772 22805 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid...

> > haven't looked at it if there is any personnal data. > > You can send to email at > > https://github.com/streetcomplete/StreetComplete/blob/e34f3b5163d4c443c6436fddb531c1116c0529a7/app/src/main/java/de/westnordost/streetcomplete/ApplicationModule.kt#L17 > if you prefer to not make...

> But it is not a stack trace. Is there no stack trace? That error just means that somewhere in native code, a process wasn't able to assign memory. ```...

Thanks a lot for your explanation! But this is strange as it only happens on StreetComplete... :thinking: > I suggest to report this to GrapheneOS developers or maybe first look...

So the bug seems to be caused by StreetComplete itself: https://github.com/GrapheneOS/os-issue-tracker/issues/1362#issuecomment-1208269870 It is a "write after free bug" in the app, so something that needs to be fixed on the...

> This is a write-after-free or buffer overflow bug in your app. When an allocation is freed with hardened_malloc, the memory is zeroed. When allocations are created, hardened_malloc checks that...

> > > See https://github.com/grote/Transportr/tree/maplibre for the current WIP implementation which still has some issues with GPS fix, especially with changing location permissions (I had to rewrite part of that...

> I just built the maplibre and tried it on a real device and didn't noticed any bug... What precise bug did you encouter? Oh I encountered a bug that...