android/tester: Fix memory leak using close() Use device->close() to free device structure. This is the way other Android devices are closed. Fixes following warnings: ... ==26231== 80 bytes in 1 blocks are definitely lost in loss record 25 of 31 ==26231== at 0x4C2A2DB: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==26231== by 0x40F153: open_bluetooth (hal-bluetooth.c:800) ==26231== by 0x40C8D8: setup (android-tester.c:835) ==26231== by 0x40CB20: setup_socket_interface_enabled (android-tester.c:1166) ==26231== by 0x409C15: setup_callback (tester.c:373) ==26231== by 0x4E7C3B5: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3800.1) ==26231== by 0x4E7C707: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3800.1) ==26231== by 0x4E7CB09: g_main_loop_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3800.1) ==26231== by 0x40A83C: tester_run (tester.c:784) ==26231== by 0x40362A: main (android-tester.c:1643) ...

Diffstat

1 files changed, 5 insertions(+), 0 deletions(-)