Hello.
If JACK server is stopped while example tool is running, there is memory leak in order of 100...200k bytes.
This is extra memory leak, in addition to 96 bytes of JACK's itself.
The example tools show this issue, are, at least: jack_simple_client, jack_rec, jack_cpu_load, jack_thru_client.
How to reproduce:
-
Git clone and compile the tools.
-
Start JACK server.
-
Use
valgrind ./jack_simple_client
-
While client is running, stop JACK server (like using qjackctl -> Stop).
- Expected result:
valgrind shows 96 bytes leak (example: like when regular client exit while JACK server is still running).
- Obtained result:
valgrind says in use at exit: 122,790 bytes.
It is particularly important to have at least one example tool with "correct" behaviour (no more than 96 bytes leak) at exit when server is lost, due to examples are useful for create other code based on it. Please fix jack_simple_client if possible.
Thanks!
P.S. Archlinux x64, jackdmp version 1.9.22 tmpdir /dev/shm protocol 9
Hello.
If JACK server is stopped while example tool is running, there is memory leak in order of 100...200k bytes.
This is extra memory leak, in addition to 96 bytes of JACK's itself.
The example tools show this issue, are, at least:
jack_simple_client,jack_rec,jack_cpu_load,jack_thru_client.How to reproduce:
Git clone and compile the tools.
Start JACK server.
Use
valgrind ./jack_simple_client
While client is running, stop JACK server (like using
qjackctl-> Stop).valgrindshows 96 bytes leak (example: like when regular client exit while JACK server is still running).valgrindsays in use at exit: 122,790 bytes.It is particularly important to have at least one example tool with "correct" behaviour (no more than 96 bytes leak) at exit when server is lost, due to examples are useful for create other code based on it. Please fix
jack_simple_clientif possible.Thanks!
P.S. Archlinux x64, jackdmp version 1.9.22 tmpdir /dev/shm protocol 9