Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64467 - [pulseaudio] Possible memory leak in PulseAudio

Attached to Project: Arch Linux
Opened by Gabriel Ziegler (gabrielziegler) - Tuesday, 12 November 2019, 02:15 GMT
Last edited by David Runge (dvzrv) - Tuesday, 19 November 2019, 21:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce: leave the computer running with PulseAudio for a few hours and check on on HTOP memory usage.
I have caught PulseAudio consuming more than 4gb of RAM many times. Killing the process with pulseaudio -k and restarting it solve it.

I am running on:
i3
Manjaro Linux x86_64, 5.2.21-1-MANJARO (this problem was also happening on my Arch)
pulseaudio 13.0-dirty

link to my dotfiles:
https://github.com/gabrielziegler3/dotfiles

This task depends upon

Comment by Gabriel Ziegler (gabrielziegler) - Wednesday, 20 November 2019, 23:44 GMT
A screenshot of Pulseaudio job consuming more than 2Gb of memory

https://snipboard.io/4KWTa5.jpg
Comment by Gabriel Ziegler (gabrielziegler) - Wednesday, 25 March 2020, 00:30 GMT
I have found out the reason for the memory leak. It was the result of a script that I was running on my polybar.
https://github.com/polybar/polybar-scripts/tree/master/polybar-scripts/pulseaudio-tail

Loading...