Not knowing where the issue lies, here is what I know so far.
Starting firefox, opening discord, then closing the tab and clearing all data. I see in 'top' that pipewire processes stay active (this is an i7-9700):
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 100766 eyal 9 -11 317308 41856 6704 S 4.7 0.1 113:55.84 pipewire-pulse 64810 eyal 9 -11 344036 19832 8004 S 2.3 0.1 55:30.94 pipewire
The two stay at the same level of %CPU, and they were barely noticeable before visit discord.
When I close firefox the activity stops, but not earlier. Disabling all add-ons has no effect.
Using sound in other ways (firefox+youtube, vlc, etc.) does not lead to such activity.
What is keeping this activity going, and how do I stop it?
TIA
On Fri, 14 Jan 2022 13:00:13 +1100 Eyal Lebedinsky fedora@eyal.emu.id.au wrote:
Not knowing where the issue lies, here is what I know so far.
Starting firefox, opening discord, then closing the tab and clearing all data. I see in 'top' that pipewire processes stay active (this is an i7-9700):
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 100766 eyal 9 -11 317308 41856 6704 S 4.7 0.1 113:55.84 pipewire-pulse 64810 eyal 9 -11 344036 19832 8004 S 2.3 0.1 55:30.94 pipewire
The two stay at the same level of %CPU, and they were barely noticeable before visit discord.
When I close firefox the activity stops, but not earlier. Disabling all add-ons has no effect.
Using sound in other ways (firefox+youtube, vlc, etc.) does not lead to such activity.
What is keeping this activity going, and how do I stop it?
Just a guess, but I wonder if discord sets up a callback or poll for sound in firefox, so even after it is gone, the callback is still active. You could try this. If you have javascript enabled for discord, disable it after you close the tab. If this is somehow a remnant of the discord tab still active, that should clobber it. If it doesn't, then you should open a bug against firefox, because it isn't cleaning up the discord tab properly when it closes it. The sound link should be cleaned up as part of that process.
Could be way off base, but if fits the data.
On 16/01/2022 03.42, stan via users wrote:
On Fri, 14 Jan 2022 13:00:13 +1100 Eyal Lebedinsky fedora@eyal.emu.id.au wrote:
Not knowing where the issue lies, here is what I know so far.
Starting firefox, opening discord, then closing the tab and clearing all data. I see in 'top' that pipewire processes stay active (this is an i7-9700):
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 100766 eyal 9 -11 317308 41856 6704 S 4.7 0.1 113:55.84 pipewire-pulse 64810 eyal 9 -11 344036 19832 8004 S 2.3 0.1 55:30.94 pipewire
The two stay at the same level of %CPU, and they were barely noticeable before visit discord.
When I close firefox the activity stops, but not earlier. Disabling all add-ons has no effect.
Using sound in other ways (firefox+youtube, vlc, etc.) does not lead to such activity.
What is keeping this activity going, and how do I stop it?
Just a guess, but I wonder if discord sets up a callback or poll for sound in firefox, so even after it is gone, the callback is still active. You could try this. If you have javascript enabled for discord, disable it after you close the tab. If this is somehow a remnant of the discord tab still active, that should clobber it. If it doesn't, then you should open a bug against firefox, because it isn't cleaning up the discord tab properly when it closes it. The sound link should be cleaned up as part of that process.
Could be way off base, but if fits the data.
Still worth a try.
Disabling javascript completely means dicord does not really start. Doing it after it started (and top shows pipewire active) does not help, pipewire still active.
Starting firefox in safe more has no (visible) effect.
Looking at about:performance does not show any unusual activity, the only items active are task manager and Add-ons Search Detection
Quitting firefox reduces pipewire %CPU from 5% to 0% after a second or two.
I files a bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1750397
-
Eyal Lebedinsky -
stan