<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Memory leak when running multiple X instances" href="https://bugs.freedesktop.org/show_bug.cgi?id=90786#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Memory leak when running multiple X instances" href="https://bugs.freedesktop.org/show_bug.cgi?id=90786">bug 90786</a> from <a class="email" href="mailto:arun@accosted.net" title="Arun Raghavan <arun@accosted.net>"> Arun Raghavan</a> <pre>If there's a leak on our side, it's not in the PulseAudio process itself, so logs won't help. Things to try: 1. You could watch the output of 'pactl stat' as the Chrome (or whatever) process memory balloons 2. Once Chrome/whatever memory is very high, you could also copy /proc/<pid of the process>/smaps somewhere and post it 3. As Tanu suggested, running Valgrind would be the most reliable option. Unfortunately, things will be really slow under Valgrind, so you might want to see if this problem occurs with a simpler command line tool (paplay --raw /dev/zero, or gst-launch-1.0 audiotestsrc wave=silence ! pulsesink). You'd need to run this with something like: valgrind --leak-check=full --show-reachable=yes --log-file=catchtheleak.log <the program and arguments></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>