I seem to have a milder version of this. I'll attach an htop screenshot showing pulseaudio to use about 2 gigs overall and 1 gig resident memory after about three and a half days uptime. It's usually half that much after a day I'd say, whether I use audio or not. Perhaps this is a different issue but I've found no other bug report on this so far. Is there an upstream report BTW or is this thought to be caused by Ubuntu- specific patches?
I'll post the PA stats corresponding to the htop output below. I resist having run PA in valgrind for a significant amount of time as this might be required since the leak doesn't seem as large for me as for many others. I'll do it though if required but the other valgrind logs don't seem to have done any good so far so please let me know. $ pactl stat Currently in use: 3 blocks containing 158.3 KiB bytes total. Allocated during whole lifetime: 30817296 blocks containing 1.4 GiB bytes total. Sample cache size: 0 B User name: cmertes Host Name: Inara Server Name: pulseaudio Server Version: 0.9.19 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo Default Source: alsa_input.pci-0000_00_1b.0.analog-stereo ** Attachment added: "htop screenshot showing the memory usage of PA" http://launchpadlibrarian.net/35743277/pulseaudio_screenshot_crop2.png -- Pulse audio memory leak https://bugs.launchpad.net/bugs/424655 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
