random freezes after starting pipewire + pipewire-pulse, seemingly uncorrelated with audio playback or application usage
Version, Distribution, Desktop Environment:
0.3.37, Void Linux, none
Description of Problem:
Random whole-system freezes after a few hours of usage when using pipewire + pipewire-pulse. The freezes sometimes happen while playing audio or otherwise while the computer is in use, and sometimes after the computer has been left idle for a long time (I go to bed without suspending, I wake up and come back to my machine, which is now frozen: the monitor won't wake up in response to any input). Has been happening since 0.3.33 or so, and happens with 0.3.33 through 0.3.36 with Void's vanilla pipewire packages, and also with 0.3.37 built using Void's srcpkgs.
How Reproducible:
The exact amount of time it will take to freeze is quite variable, but I haven't lasted longer than about 36 hours in a while, and 9/10 times it'll happen within 4 hours.
Steps to Reproduce:
- Vanilla pipewire packages on Void.
- Run as:
PIPEWIRE_DEBUG=5 pipewire > ~/pipewire_stdout.txt 2> ~/pipewire_stderr.txt & PIPEWIRE_DEBUG=4 pipewire-pulse > ~/pipewire-pulse_stdout.txt 2> ~/pipewire-pulse_stderr.txt &
PIPEWIRE_DEBUG=5
on the pulse package results in gigabytes of logging. I have attached the logs of my last run, which resulted in a freeze while I was not at my machine. - Us the computer as normal.
Actual Results:
After a few hours, it will freeze.
Expected Results:
No freeze.
I realize I haven't given much material to work with, but system logs really don't show anything suspicious at all. Void's logging svlogtail
, dmesg
, and others have nothing in them near the time of the freeze. I'm not sure how to use gdb in a case like this where the entire system is unusable as soon as the issue arises. I'm happy to take any advice as to how to debug the problem and provide more information for solving the issue. Other than this, pipewire has been great, and I'm looking forward to resolving it so I can get back to using it all the time.
I just realized while writing this that while I had intended to reset all my configs back to the defaults when collecting the logs, I didn't actually do that correctly! I will do so and report back. In any case, I don't think any of my configs should break anything, so I'm opening the issue to track my progress in figuring this out.