jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2024-03-25T18:36:16Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/975Link voice setup callback to host (without rtp session)2024-03-25T18:36:16ZSébastien BlinLink voice setup callback to host (without rtp session)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/974Various asserts and crashes with TURN / PJNATH2024-03-25T18:29:13ZAdrien BéraudVarious asserts and crashes with TURN / PJNATHTypical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 D...Typical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Build fingerprint: 'google/cheetah/cheetah:14/AP1A.240305.019.A1/11445699:user/release-keys'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Revision: 'MP1.0'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A ABI: 'arm64'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Timestamp: 2024-03-22 14:13:31.550572829-0400
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Process uptime: 2s
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Cmdline: cx.ring
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A pid: 8414, tid: 9172, name: Thread-64 >>> cx.ring <<<
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A uid: 10352
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Abort message: '../src/pjnath/turn_session.c:740: pj_status_t pj_turn_session_alloc(pj_turn_session *, const pj_turn_alloc_param *): assertion "sess->state>PJ_TURN_STATE_NULL && sess->state<=PJ_TURN_STATE_RESOLVED" failed'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x0 0000000000000000 x1 00000000000023d4 x2 0000000000000006 x3 000000795e531320
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x4 2f333639622d6d6e x5 2f333639622d6d6e x6 2f333639622d6d6e x7 7f7f7f7f7f7f7f7f
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x8 00000000000000f0 x9 0000007d40c87200 x10 0000000000000001 x11 0000007d40cd1ba0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x12 0000007d5ac86020 x13 000000007fffffff x14 00000000009ffbec x15 00000247cba606d0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x16 0000007d40d3cfc8 x17 0000007d40d1a160 x18 000000795b0d8000 x19 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x20 00000000000023d4 x21 00000000ffffffff x22 0000000000002374 x23 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x24 000000795e5318b0 x25 000000795e5318b0 x26 000000795e531bf0 x27 00000000000fc000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x28 00000000000fe000 x29 000000795e5313a0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A lr 0000007d40cc2e48 sp 000000795e531300 pc 0000007d40cc2e74 pst 0000000000001000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A 11 total frames
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A backtrace:
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #00 pc 000000000005ee74 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #01 pc 000000000005f284 /apex/com.android.runtime/lib64/bionic/libc.so (__assert2+36) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #02 pc 0000000001922e2c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_turn_session_alloc+284) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #03 pc 000000000192a61c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #04 pc 000000000192a258 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #05 pc 000000000194d5f4 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #06 pc 00000000019414bc /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (ioqueue_dispatch_write_event+416) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #07 pc 0000000001945428 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_ioqueue_poll+1476) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #08 pc 0000000001739b98 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #09 pc 00000000000ca7cc /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #10 pc 00000000000607b0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
```Sébastien BlinFrançois-Simon Fauteux-ChapleauSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/973Flatpak: Automatic Upgrades: tag versions of jami-daemon which jami-client de...2024-03-22T09:29:01ZovariFlatpak: Automatic Upgrades: tag versions of jami-daemon which jami-client depends on>> It would be great if this Flatpak package would upgrade automatically if a newer upstream version of Jami is released.
> Not possible because of how jami-client depends on specific untagged versions of jami-daemon.
https://github.co...>> It would be great if this Flatpak package would upgrade automatically if a newer upstream version of Jami is released.
> Not possible because of how jami-client depends on specific untagged versions of jami-daemon.
https://github.com/flathub/net.jami.Jami/issues/86https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972Modified contact profile synchronization2024-03-19T13:01:46ZPierre NicolasModified contact profile synchronizationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1402#note_48719
> The display name and the profile picture, which I have assigned to my contact myself, have not been synchronised.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1402#note_48719
> The display name and the profile picture, which I have assigned to my contact myself, have not been synchronised.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/970Video camera stream is black when hardware acceleration is enabled2024-03-08T13:26:13ZPaul Le Guen de KerneizonVideo camera stream is black when hardware acceleration is enabled## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue i...## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
## Bug report form
## Describe your environment
Please specify the following:
- OS: Ubuntu 22.04.4 LTS
- Jami version: 202402141827
- What build you are using: jami.net
## Steps to reproduce
1. Enable hardware acceleration in parameters with 960x540 resolution
2. Start a video call
- Actual result: My video camera stream is black on the Jami screen of other contacts in the meeting. However, I can see myself on my Jami screen. Must disable hardware acceleration to solve the problem or change the video resolution to 1280x720
- Expected result: Other people can see my camera video stream instead of a black screen.
## Additional information
- With Jami enable with `--debug`, this log appeared:
```
[1709890977.592|52761|accel.cpp :298 ] Failed to push frame to GPU: Invalid argument
[1709890977.593|52761|media_encoder.cpp :438 ] Fail to get frame
[1709890977.593|52761|video_sender.cpp :87 ] encoding failed
```
- The issue appears whatever camera I use
- My laptop is a Lenovo P14S with AMD GPU and same hardware
- We achieve to reproduce the same bug with Fedora 39
On contact side:
![Screenshot_from_2024-03-08_11-29-49](/uploads/f93d51095c449899708f64255c9f4850/Screenshot_from_2024-03-08_11-29-49.png)
On my side:
![Screenshot_from_2024-03-08_11-29-48](/uploads/f5672232032c2ce2a9671ebf44825c2e/Screenshot_from_2024-03-08_11-29-48.png)
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/966Merge bind and attach methods2024-02-28T15:12:19ZSébastien BlinMerge bind and attach methodshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/965Rename addParticipant/removeParticipant (callId)2024-02-28T15:12:09ZSébastien BlinRename addParticipant/removeParticipant (callId)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/964Remove takeOverMediaSourceControl2024-02-28T15:11:11ZSébastien BlinRemove takeOverMediaSourceControlhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/963Remove method setLocalHostDefaultMediaSource (not understandable)2024-02-28T15:10:32ZSébastien BlinRemove method setLocalHostDefaultMediaSource (not understandable)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/962Simplify Conference construction. Never attach Host, then attach Host in vide...2024-02-28T15:09:50ZSébastien BlinSimplify Conference construction. Never attach Host, then attach Host in video OR audiohttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/960Call-swarm: Too long timeout for need host2024-03-28T00:05:08ZSébastien BlinCall-swarm: Too long timeout for need host# Scenario
+ Bob call Alice (host, offline)
# Current result
The host popup is taking 30s to come (for busy signal)
# Expected
I guess 10s would be enough# Scenario
+ Bob call Alice (host, offline)
# Current result
The host popup is taking 30s to come (for busy signal)
# Expected
I guess 10s would be enough2024-02-29https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/959Call-Swarm/Rdv: wrong audio is attached2024-03-28T00:05:08ZSébastien BlinCall-Swarm/Rdv: wrong audio is attached# Scenario
+ In a call swarm (alice is the host), bob calls
+ Alice is detached, but audio is playing
# Expected
Alice should not ear anything, Bob should not ear alice# Scenario
+ In a call swarm (alice is the host), bob calls
+ Alice is detached, but audio is playing
# Expected
Alice should not ear anything, Bob should not ear alicehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/958Call-swarm: Joining in audio make the host join2024-03-25T18:36:16ZSébastien BlinCall-swarm: Joining in audio make the host join# Scenario
* Alice, Bob in a swarm
* Alice is default host
* Bob joins in audio
# Expected
Alice doesn't join the call
# Current
Alice is attached# Scenario
* Alice, Bob in a swarm
* Alice is default host
* Bob joins in audio
# Expected
Alice doesn't join the call
# Current
Alice is attachedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/957Call-swarm: join in audio fails2024-02-26T20:30:19ZSébastien BlinCall-swarm: join in audio fails# Scenario
* Alice, Bob, Carla in a swarm
* Alice is default host
* Bob call in audio
* Carla calls (audio or video)
# Expected result
Carla should ear Bob
# Current result
No sound# Scenario
* Alice, Bob, Carla in a swarm
* Alice is default host
* Bob call in audio
* Carla calls (audio or video)
# Expected result
Carla should ear Bob
# Current result
No soundhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/954DHT Proxy full pass2024-03-28T00:05:08ZSébastien BlinDHT Proxy full pass# TODO
Try to reproduce any issue/find any scenario# TODO
Try to reproduce any issue/find any scenarioSébastien BlinFrançois-Simon Fauteux-ChapleauSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/952improve configurationMtx contention2024-03-28T00:05:08ZSébastien Blinimprove configurationMtx contentionconfigurationMtx_ is locked for a loooot of things and probably a lot of un-necessary causing the daemon to take a lot of time and this should be improvedconfigurationMtx_ is locked for a loooot of things and probably a lot of un-necessary causing the daemon to take a lot of time and this should be improvedAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/950--disable-natpmp doesn't work anymore2024-02-15T14:34:27ZSébastien Blin--disable-natpmp doesn't work anymoreprobably since it's done in dhtnetprobably since it's done in dhtnethttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/930POC: new linking account mechanism2024-03-28T00:05:08ZSébastien BlinPOC: new linking account mechanism# Goal
Do not use the DHT to transfer the account archive while linking a new device, but rather use a p2p link between the new and old device
# TODO
+ Define architecture
+ POC (client)
+ add docs to docs.jami.net
+ Finalize daemon c...# Goal
Do not use the DHT to transfer the account archive while linking a new device, but rather use a p2p link between the new and old device
# TODO
+ Define architecture
+ POC (client)
+ add docs to docs.jami.net
+ Finalize daemon code
+ Ping design & clients to implement the featureKessler DuPont-TeevinAdrien BéraudKessler DuPont-Teevin2024-01-31https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/927Android: Same contact multiple times (multi device related?)2023-12-16T18:01:12ZElysAndroid: Same contact multiple times (multi device related?)Desktop (Beta): 202312142117
Android (20231213-01)
Steps to reproduce:
- You are using the same Jami account ("Jamiaccount1") on different devices - and you always have your own Jami account in the contact list (so you can make calls /...Desktop (Beta): 202312142117
Android (20231213-01)
Steps to reproduce:
- You are using the same Jami account ("Jamiaccount1") on different devices - and you always have your own Jami account in the contact list (so you can make calls / send messages "Jamiaccount1" device 1 <-> "Jamiaccount1" device 2)
- - only the desktop device 1 also has another own account "Jamiaccount2": "Jamiaccount1" is in the contact list of "Jamiaccount2" (and the other direction); however "Jamiaccount2" account does NOT have it's own account in the contact list?
- BUT you always use the same two devices (desktop and android phone) for weeks
- Now you are using a different desktop device (3) that only uses "Jamiaccount2" (device 3)contact ("Jamiaccount1") is already in the contact list of "Jamiaccount2" (device 1,2) because you've added "Jamiaccount2" on another device
- Once you open Jami on desktop - Jami on Android will create another same contact of "Jamiaccount1" and if you tap the duplicated contact the chatview will stuck at "Downloading conversation from peer" (even if you restart Jami on Android)
Screenshot (of the Android device)
![Jamitwice1](/uploads/32a667c3f81374effdc83094bcd1c85c/Jamitwice1.png)
Detail:
![Jamitwice2](/uploads/456f273bf0080e14b7b569cdb820656e/Jamitwice2.png)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/926Crash in OpenSSL (JAMS deletion) - heap use after free2023-12-05T21:03:14ZSébastien BlinCrash in OpenSSL (JAMS deletion) - heap use after free```
#0 0x7f00b503a396 in __interceptor_memcpy ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827
#1 0x7f00a10e1361 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xe1361)
#2 0x7f00a10d234a (/lib/x86_...```
#0 0x7f00b503a396 in __interceptor_memcpy ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827
#1 0x7f00a10e1361 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xe1361)
#2 0x7f00a10d234a (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd234a)
#3 0x7f00a10d5344 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd5344)
#4 0x7f00a10d5b3c in BIO_read_ex (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd5b3c)
#5 0x7f00a10d5344 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd5344)
#6 0x7f00a10d54c6 in BIO_read (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd54c6)
#7 0x7f00a10bc059 in asn1_d2i_read_bio (/lib/x86_64-linux-gnu/libcrypto.so.3+0xbc059)
#8 0x7f00a1268716 (/lib/x86_64-linux-gnu/libcrypto.so.3+0x268716)
#9 0x7f00a125aa62 (/lib/x86_64-linux-gnu/libcrypto.so.3+0x25aa62)
#10 0x7f00a11697ba (/lib/x86_64-linux-gnu/libcrypto.so.3+0x1697ba)
#11 0x7f00a1169a90 in OSSL_DECODER_from_bio (/lib/x86_64-linux-gnu/libcrypto.so.3+0x169a90)
#12 0x7f00a1169dbd in OSSL_DECODER_from_data (/lib/x86_64-linux-gnu/libcrypto.so.3+0x169dbd)
#13 0x7f00a123fae3 (/lib/x86_64-linux-gnu/libcrypto.so.3+0x23fae3)
#14 0x7f00a10ceb9a (/lib/x86_64-linux-gnu/libcrypto.so.3+0xceb9a)
#15 0x7f00a10d03e7 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd03e7)
#16 0x7f00a10ced18 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xced18)
#17 0x7f00a10d03e7 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd03e7)
#18 0x7f00a10ced18 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xced18)
#19 0x7f00a10cf492 in ASN1_item_d2i_ex (/lib/x86_64-linux-gnu/libcrypto.so.3+0xcf492)
#20 0x7f00a15e8132 (/lib/x86_64-linux-gnu/libssl.so.3+0x67132)
#21 0x7f00a15e4a04 (/lib/x86_64-linux-gnu/libssl.so.3+0x63a04)
#22 0x7f00a15e6607 (/lib/x86_64-linux-gnu/libssl.so.3+0x65607)
#23 0x7f00a5176230 in asio::ssl::detail::engine::perform(int (asio::ssl::detail::engine::*)(void*, unsigned long), void*, unsigned long, std::error_code&, unsigned long*) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1d76230)
#24 0x7f00a5135430 in asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::any_io_executor>, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>::operator()(std::error_code, unsigned long, int) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1d35430)
#25 0x7f00a514062b in asio::detail::reactive_socket_recv_op<asio::mutable_buffers_1, asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::any_io_executor>, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1d4062b)
#26 0x7f00a501e62b in asio::detail::epoll_reactor::descriptor_state::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1c1e62b)
#27 0x7f00a3e7ebb8 in asio::detail::scheduler_operation::complete(void*, std::error_code const&, unsigned long) /home/sblin/Projects/jami-project/client-qt/daemon/contrib/x86_64-linux-gnu/include/asio/detail/scheduler_operation.hpp:39
#28 0x7f00a3e85aa6 in asio::detail::scheduler::do_run_one(asio::detail::conditionally_enabled_mutex::scoped_lock&, asio::detail::scheduler_thread_info&, std::error_code const&) /home/sblin/Projects/jami-project/client-qt/daemon/contrib/x86_64-linux-gnu/include/asio/detail/impl/scheduler.ipp:492
#29 0x7f00a3e84ed9 in asio::detail::scheduler::run(std::error_code&) /home/sblin/Projects/jami-project/client-qt/daemon/contrib/x86_64-linux-gnu/include/asio/detail/impl/scheduler.ipp:209
#30 0x7f00a3e86298 in asio::io_context::run() (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0xa86298)
#31 0x7f00a3e3aaef in operator() /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:464
#32 0x7f00a3e73fb3 in __invoke_impl<void, jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > /usr/include/c++/11/bits/invoke.h:61
#33 0x7f00a3e73f76 in __invoke<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > /usr/include/c++/11/bits/invoke.h:96
#34 0x7f00a3e73f23 in _M_invoke<0> /usr/include/c++/11/bits/std_thread.h:259
#35 0x7f00a3e73ef7 in operator() /usr/include/c++/11/bits/std_thread.h:266
#36 0x7f00a3e73edb in _M_run /usr/include/c++/11/bits/std_thread.h:211
#37 0x7f00a30dc252 (/lib/x86_64-linux-gnu/libstdc++.so.6+0xdc252)
#38 0x7f00a2c94ac2 in start_thread nptl/pthread_create.c:442
#39 0x7f00a2d26a3f (/lib/x86_64-linux-gnu/libc.so.6+0x126a3f)
0x62a0001c90e7 is located 3815 bytes inside of 21848-byte region [0x62a0001c8200,0x62a0001cd758)
freed by thread T0 here:
#0 0x7f00b50b4537 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:127
#1 0x7f00a10f5174 in BUF_MEM_free (/lib/x86_64-linux-gnu/libcrypto.so.3+0xf5174)
previously allocated by thread T24 here:
#0 0x7f00b50b4887 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x7f00a10f6ca5 in BUF_MEM_grow (/lib/x86_64-linux-gnu/libcrypto.so.3+0xf6ca5)
Thread T24 created by T0 here:
#0 0x7f00b5058685 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216
#1 0x7f00a30dc328 in std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (/lib/x86_64-linux-gnu/libstdc++.so.6+0xdc328)
#2 0x7f00a3e3b424 in jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&) /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:461
#3 0x7f00a3e90a5e in std::_MakeUniq<jami::Manager::ManagerPimpl>::__single_object std::make_unique<jami::Manager::ManagerPimpl, jami::Manager&>(jami::Manager&) /usr/include/c++/11/bits/unique_ptr.h:962
#4 0x7f00a3e3fbfe in jami::Manager::Manager() /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:755
#5 0x7f00a3e3f94b in jami::Manager::instance() /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:728
#6 0x7f00a3f83bee in libjami::init(libjami::InitFlag) /home/sblin/Projects/jami-project/client-qt/daemon/src/ring_api.cpp:69
#7 0x5637e3d41766 in InstanceManagerInterface::InstanceManagerInterface(bool) /home/sblin/Projects/jami-project/client-qt/src/libclient/qtwrapper/instancemanager.cpp:54
#8 0x5637e4e588c7 (/home/sblin/Projects/jami-project/client-qt/build/jami+0x1d568c7)
SUMMARY: AddressSanitizer: heap-use-after-free ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827 in __interceptor_memcpy
Shadow bytes around the buggy address:
0x0c54800311c0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c54800311d0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c54800311e0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c54800311f0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031200: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x0c5480031210: fd fd fd fd fd fd fd fd fd fd fd fd[fd]fd fd fd
0x0c5480031220: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031230: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031240: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031250: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031260: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==596032==ABORTING
```