Re: pipewire memory usage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I can get it as high as that too but then it stays there and doesn't really grow anymore so it does not seem like
it's leaking. Maybe it's the way things are done, there is a lot of ldopen and memfd/mmap.

Wim

On Mon, Dec 13, 2021 at 11:42 PM Dominique Martinet <asmadeus@xxxxxxxxxxxxx> wrote:
Wim Taymans wrote on Mon, Dec 13, 2021 at 09:22:42AM +0100:
> There was a leak in 0.3.40 that could explain this, see
> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1840
>
> Upcoming 0.3.41 will have this fixed. At least I can't reproduce this
> anymore with the test you posted below.

Thanks for testing!

I've also taken the time of rebuilding pipewire from source (current
master, just on top of 0.3.41) but unfortunately it doesn't look like it
solves the issue here, so it must be something specific in my
environment.

fresh start:
myuser  335184  1.0  0.0  56384 11596 ?        S<sl 07:36   0:00 /opt/pipewire/bin/pipewire
myuser  335197  2.7  0.0  36000 11480 ?        S<l  07:36   0:00 /usr/bin/pipewire-media-session
myuser  335208  0.5  0.0  31312  6428 ?        S<sl 07:36   0:00 /opt/pipewire/bin/pipewire-pulse

after running 100 mpv like last time:
myuser  335184  5.3  0.3 174836 63360 ?        S<sl 07:36   0:01 /opt/pipewire/bin/pipewire
myuser  335197  1.6  0.0  36708 12336 ?        S<l  07:36   0:00 /usr/bin/pipewire-media-session
myuser  335208  9.2  2.1 666020 341196 ?       S<sl 07:36   0:01 /opt/pipewire/bin/pipewire-pulse



`pactl stat` is happy though:
Currently in use: 89 blocks containing 3.4 MiB bytes total.
Allocated during whole lifetime: 89 blocks containing 3.4 MiB bytes total.
Sample cache size: 0 B

I've run out of free time this morning but since it's not a known issue
I'll debug this a bit more after getting home tonight and report an
issue proper.
Since it's easy to reproduce here I'm sure I'll find the cause in no
time...

--
Domnique
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux