You are not logged in.

#1 2023-02-10 14:47:47

xfqt
Member
From: .de
Registered: 2022-01-12
Posts: 13

Wireplumber eating system RAM - Best approach?

Hello everyone,

I'm using arch on my desktop and recently my wireplumber has been acting up. Starting weeks ago, so I can't precisely give any dates or version numbers, my system started running OOM. At first I thought this was just from steam and proton, so I upgraded my system to 32 GB. But since the upgrade the system did still crash at seemingly random. Everything freezes and becomes completly unresponsive. There is nothing in journalctl. The only remedy is to force shut-off the computer.

By chance I saw the memory was full in my panel and somehow managed to get htop up as the system became gradually slower. On top of that list was wireplumber, sitting at a comfortable 18GB of ram. Since then I managed to stop a freeze two times by killing wireplumber early enough. I am using pipewire with pipewire-pulse. I can't remember configuring anything special with wireplumber.

Now sitting at my computer and manually monitoring process ram usage doesn't really seem like a good approach. There are mentions of the integraded linux oom killer, there are other programs such als earlyoom and I've read about creating groups to set limits for ram usage. What would be the best way to stop my system from freezing? I feel like an OOM killer might be interrupting me at bad times wheres creating groups doesn't exactly seem like an easy task. I think it might the best way anyway since I don't see how wireplumber would need several gigabyte of system memory in the first place.


Versions in use:
Wireplumber

local/libwireplumber 0.4.13-1
local/wireplumber 0.4.13-1
local/libwireplumber 0.4.13-1

Pipewire

local/pipewire 1:0.3.65-6
local/pipewire-alsa 1:0.3.65-6
local/pipewire-audio 1:0.3.65-6
local/pipewire-pulse 1:0.3.65-6
local/wireplumber 0.4.13-1

Kernel

Linux arch 6.1.8-arch1-1 

Offline

#2 2023-02-10 15:06:11

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,451

Re: Wireplumber eating system RAM - Best approach?

Anything in the logs on why it would be acting up?

journalctl -b --user-unit=wireplumber

do you have a webcam? There have been some issues with libcamera integration and wireplumber, might want to try and disable that see https://gitlab.freedesktop.org/pipewire … issues/385 and particularly https://gitlab.freedesktop.org/pipewire … te_1672216 for how to disable libcamera.

General note that might be contributing, why is your kernel outdated and have you updated so you are technically running on a kernel that does not have access to it's modules?

Offline

#3 2023-02-10 15:17:26

xfqt
Member
From: .de
Registered: 2022-01-12
Posts: 13

Re: Wireplumber eating system RAM - Best approach?

The log doesn't contain anything hinting before the crash. One error is shown twice every ten minutes, 3 seconds apart:

 <WpPortalPermissionStorePlugin:0x5568b08eed90> Failed to call Lookup: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.Permiss>

The webcam point is interesting though, I do have a USB webcam with a mic showing up in pavucontrol. I'll try disabling that.

As for the kernel version, I may have updated the system as I was writing this post (not in line with forum guidelines I'm afraid), so there might be a little difference. But I did a lot of updates in all of the time of the system freezing so I doubt there's a link.

Offline

#4 2023-02-10 15:19:21

seth
Member
Registered: 2012-09-03
Posts: 64,312

Re: Wireplumber eating system RAM - Best approach?

https://gitlab.freedesktop.org/pipewire … issues/385 - libcamera?

Edit: F5 …

Last edited by seth (2023-02-10 15:19:54)

Offline

Board footer

Powered by FluxBB