Are any Valgrind traces available showing leaks inside libpulse?

Sorry, the attachments in the KDE bug seem to contain useful traces.

if there are a fix version of pulseaudio.
could it release a version that ubuntu 12.10 could installed.
the newest pulseaudio 3.0 it just could install in ubuntu 13.04

i have try to use the valgrind to detect the memory leak.
but i only can use the pulseaudio -k to stop the pulseaudio.

is there a test way to normally stop the pulseaudio ?
because when i use the pulseaudio -k
it did not show the result.

(In reply to comment #4)
> i have try to use the valgrind to detect the memory leak.
> but i only can use the pulseaudio -k to stop the pulseaudio.
> 
> is there a test way to normally stop the pulseaudio ?

pactl exit

> because when i use the pulseaudio -k
> it did not show the result.

Running pulseaudio in Valgrind won't help getting the kmix leaks fixed (unless the bugs affect both pulseaudio and libpulse). As I said, the KDE bug already has a useful Valgrind report, so there's no pressing need to generate more reports (it's not harmful either, though).

is there any progress about the memory leak?

Going through the valgrind logs in the KDE bug, I see no directly/indirectly lost memory that is allocated by libpulse. All the leaks seem related to the kmix application itself.. I did a quick valgrind check on pavucontrol and paplay to make sure we're not leaking memory.

If anyone cares to, it would be nice to do a proper teardown of all allocated objects when shutting down pavucontrol. That should remove all "still reachable" pa_xmalloc() traces.