As per the description, and as per the report I initially made at https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2660 - wireplumber will sometimes "go nuts" and just sit there consuming a core, requiring it to be restarted. At the gitlab issue, there's a recommendation that I raise an issue here asking for a backport of https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/398 to the current stable pipewire package, so that's what I'm doing here. Reproducible: Sometimes Steps to Reproduce: 1. Run pipewire 2. I _think_ that switching default sinks via pw-metadata may trigger it, but it's not reliable Actual Results: wireplumber spins on a core, consuming it Expected Results: wireplumber should straigten up and fly right
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=916a0b55068c037e5871ab411da6c3a2e5444349 commit 916a0b55068c037e5871ab411da6c3a2e5444349 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-08-26 10:51:07 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-08-26 10:51:07 +0000 media-video/wireplumber: backport 100% CPU loop fixes Closes: https://bugs.gentoo.org/866551 Signed-off-by: Sam James <sam@gentoo.org> .../files/wireplumber-0.4.11-loop.patch | 147 +++++++++++++++++++++ .../wireplumber/wireplumber-0.4.11-r3.ebuild | 131 ++++++++++++++++++ 2 files changed, 278 insertions(+)
Thank you!
