Branch: refs/heads/master Home: https://github.com/bluez/bluez Commit: 09e39a7d6dca8041f3723ee9020c54b94c0c8d47 https://github.com/bluez/bluez/commit/09e39a7d6dca8041f3723ee9020c54b94c0c8d47 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2024-06-03 (Mon, 03 Jun 2024) Changed paths: M src/shared/csip.c Log Message: ----------- shared/csip: Fix memory leak This fixes the following leak: 102 bytes in 6 blocks are definitely lost in loss record 660 of 909 at 0x484282F: malloc (vg_replace_malloc.c:446) by 0x5A078B: util_malloc (util.c:46) by 0x649162: read_sirk (csip.c:485) by 0x5C74FA: read_cb (gatt-client.c:2713) by 0x5C4137: handle_rsp (att.c:880) by 0x5C4137: can_read_data (att.c:1072) by 0x65DDA4: watch_callback (io-glib.c:157) by 0x49656AB: ??? (in /usr/lib64/libglib-2.0.so.0.8000.2) by 0x49C6707: ??? (in /usr/lib64/libglib-2.0.so.0.8000.2) by 0x496B666: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.8000.2) by 0x65FE3D: mainloop_run (mainloop-glib.c:66) by 0x6605A3: mainloop_run_with_signal (mainloop-notify.c:188) by 0x31DEFA: main (main.c:1468) Commit: 7e9816dd8c219f26f52fcb46fa13ecddfcf2d526 https://github.com/bluez/bluez/commit/7e9816dd8c219f26f52fcb46fa13ecddfcf2d526 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2024-06-03 (Mon, 03 Jun 2024) Changed paths: M src/shared/gatt-db.c M src/shared/gatt-db.h Log Message: ----------- shared/gatt-db: Introduce gatt_db_clone This introduces gatt_db_clone which can be used to clonse/deep copy and existing database. Commit: cbe4144dea6fde87e13016c2861c9ba5f75f716f https://github.com/bluez/bluez/commit/cbe4144dea6fde87e13016c2861c9ba5f75f716f Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2024-06-03 (Mon, 03 Jun 2024) Changed paths: M src/device.c M src/device.h M src/set.c M src/shared/gatt-db.c Log Message: ----------- set: Attempt to use existing set gatt-db Most sets should be clone of each other, or at least very similar, so this attempts to clone the existing gatt-db of the first member found when connecting new sets, this substantially speed up the process of bonding sets if their database matches which is something that is currently ranging from 20-30 seconds depending on the manufacturer and with this changes it cuts 5-10 seconds by bypassing discovery all procedure of other members. If the dbs don't really match bt_gatt_client instance will attempt to rediscover the ranges that don't match. Compare: https://github.com/bluez/bluez/compare/60b482c3c9ba...cbe4144dea6f To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
