This bug report is now very old, but is this bug still present?
Here is why I ask.
Running valgrind on a C program - a program that I adapted from someone
else - showed a lot of possible leaks. But I learnt from this the
present bug report to do 'snd_config_update_free_global()'. Having done
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-lib (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017375
Title:
** Attachment added: alsa-async.c
https://bugs.launchpad.net/bugs/1017375/+attachment/3203275/+files/alsa-async.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017375
Title:
memory leaks in
oops here is the valgrind output.
** Attachment added: valgrind.txt
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1017375/+attachment/3203276/+files/valgrind.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some of the 'leaks' can be removed by calling
snd_config_update_free_global(), but this still leaves many reachable
blocks...
updated test code attached: alsa-async.c
come of the valgrind output...
==5312== Memcheck, a memory error detector
==5312== Copyright (C) 2002-2011, and GNU GPL'd, by
