Description of problem:

After having the system running for several hours, pipewire-pulse seems to have locked up somehow and fills the journal with messages like this:
pipewire-pulse[2316]: loop 0x561c9688d6c8: queue full 0

Playing audio is then not possible anymore. Over the course of an evening, this produced several gigabytes(!) of log messages.

Restarting it with
$ systemctl --user restart pipewire-pulse.service
solves the problem temporarily. The call also hangs for several seconds, probably waiting for a timeout.

Version-Release number of selected component (if applicable):

pipewire.x86_64                                   0.3.27-1.fc34
pipewire-alsa.x86_64                              0.3.27-1.fc34
pipewire-gstreamer.x86_64                         0.3.27-1.fc34
pipewire-jack-audio-connection-kit.x86_64         0.3.27-1.fc34
pipewire-libs.x86_64                              0.3.27-1.fc34
pipewire-pulseaudio.x86_64                        0.3.27-1.fc34
pipewire-utils.x86_64                             0.3.27-1.fc34

How reproducible:

I am not sure how often this has actually happened yet. I noticed it at least two times.

Steps to Reproduce:
1. Leave the system running for some time and use it normally (suspending and resuming might also have to do something with it)
2. Check journal output and/or try to play audio

Actual results:

Audio stops working and journal fills up.

Expected results:

Audio keeps working and pipewire-pulse does not log excessively.