Group chats crash the app on AXP.OS

[freedomlibrelover]

As requested, I create a new issue. I use version 1.0.256, the latest one on F-Droid (updated 3 days ago).

Here is what happens when I try to join tox support group:
At first I am alone in the group, after some time it loads as TRIfA Community, but I never see any messages. Then I can make a few posts like "hi" or "is this working" but after that I get thrown out to the main app menu with the following message at the top:

Successfully loaded native library
Native code compiled with ABI:arm64-v8a
c-toxcore:v0.2.19,jni-c-toxcore:v.0.99.96

After that if I try to enter the group chat again the app immediately crashes. And after that after every app launch it just crashes in a few seconds. If I hold a finger on the group chat and select "leave" without entering it in these few seconds, the app stops crashing.

Logs sent via tox. The issue is related to malloc/memory corruption.

[zoff99]

@freedomlibrelover can you install and try it with the nightly debug version:
https://github.com/zoff99/ToxAndroidRefImpl/releases/download/nightly/TRIfA-nightly.apk

it will install along side of trifa, with a different app id.
its doing an insane amout of logging, but it should better show what the last thing is that happens before the crash.
the previous stacktrace does not show any trifa component.

[freedomlibrelover]

@freedomlibrelover can you install and try it with the nightly debug version

I've installed it and result is the same. I am sending you the log via tox.

[zoff99]

@freedomlibrelover can you send a new temp toxid again please?

[freedomlibrelover]

Just in case, my last messages to you are marked as yellow, not green, for a day. Next to your profile it shows a green circle inside of a red circle - I can't find in the app what that means. Also, when sending a message to atox from trifa, it works but there is a series of random extra symbols at the end of each message, but not vice-versa.

[zoff99]

@freedomlibrelover can you please try the newest nightly again? it has now even more logging. maybe this time it will show where the crash happens

[freedomlibrelover]

Logs sent

[zoff99]

@freedomlibrelover its still inconclusive. if you can lets try it one more time with the latest nightly.

[freedomlibrelover]

Okay, I will send them tomorrow. Sorry for the delay.

[freedomlibrelover]

Files sent

[zoff99]

@freedomlibrelover
i added still more logging and also it logs every SQL statement. so if you can, would you try it with the latest nightly again? but this time please be very careful with the logs since the SQL statments may contain sensitive information and data.
have a look through the logs before you send them to me

[freedomlibrelover]

Ok, I will send data today or tomorrow