Crashes randomly or when firefox is restarted after a video is played.

[aspizu]

1. Open firefox
2. Play video
3. Close firefox
4. Open firefox

EE will crash.

fish: Job 1, 'easyeffects --gapplication-serv…' terminated by signal SIGKILL (Forced quit)

[wwmm]

Try to run it in debug mode so we can have some idea about what is being done when the crash happens https://github.com/wwmm/easyeffects/wiki/Reporting-Bugs#basic-logs. Remember to kill EasyEffects first. I use Firefox everyday to watch videos and no crashes happens on my side. So more information will be needed to understand what is going on.

[aspizu]

it stopped crashing

[aspizu]

(easyeffects:63392): easyeffects-DEBUG: 19:19:33.542:   pipe_manager.cpp:213    Stream/Output/Audio 121 Firefox has been removed
(easyeffects:63392): easyeffects-DEBUG: 19:19:43.476:   stream_output_effects.cpp:159   No app linked to our device wants to play. Unlinking our filters.
(easyeffects:63392): easyeffects-DEBUG: 19:19:43.476:   stream_output_effects.cpp:317   disconnecting the equalizer filter from PipeWire
(easyeffects:63392): easyeffects-DEBUG: 19:19:43.478:   pipe_manager.cpp:213     158 ee_soe_equalizer has been removed
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.961:   pipe_manager.cpp:1167   Stream/Output/Audio 167 Firefox with serial 5412 has been added
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.963:   pipe_manager.cpp:900    new metadata property: 167, target.node, Spa:Id, 141
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.963:   pipe_manager.cpp:900    new metadata property: 167, target.object, Spa:Id, 5281
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.970:   pipe_manager.cpp:1207   Firefox port 150 is connected to easyeffects_sink port 124
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.970:   pipe_manager.cpp:1207   Firefox port 143 is connected to easyeffects_sink port 71
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.971:   stream_output_effects.cpp:150   At least one app linked to our device wants to play. Linking our filters.
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.973:   plugin_base.cpp:370     soe: equalizer successfully connected to PipeWire graph
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.973:   pipe_manager.cpp:1207   easyeffects_sink port 44 is connected to ee_soe_equalizer port 133
(easyeffects:63392): easyeffects-DEBUG: 19:19:54.973:   pipe_manager.cpp:1207   easyeffects_sink port 122 is connected to ee_soe_equalizer port 139
(easyeffects:63392): easyeffects-DEBUG: 19:40:02.114:   pipe_manager.cpp:213    Stream/Output/Audio 167 Firefox has been removed

fish: Job 1, 'G_MESSAGES_DEBUG=easyeffects ea…' terminated by signal SIGKILL (Forced quit)

[wwmm]

Which EasyEffects version are you using?

[aspizu]

❯ easyeffects --version
Unknown option --version

[wwmm]

You can see the version in its about windowand in the first lines printed by its logs. This command you tried won't work.

[wwmm]

terminated by signal SIGKILL (Forced quit)

This feels more like EasyEffects being killed by something than a crash.

[aspizu]

All things should have a --version option. The version is 7.1.0. I am on Arch Linux. pipewire version is 0.3.83.

[wwmm]

I am on Arch Linux. pipewire version is 0.3.83.

Hmm... I am also on Arch Linux... But I usually use the package built from AUR to test our master branch. I suggest you try to install the AUR package to see if it still crashes. Or if it keeps being killed. It does not seem to be a crash.

[fengints]

getting the same, problem with fish ? fish: Job 4, 'easyeffects' terminated by signal SIGKILL (Forced quit)

flatpak version exits with error code 137

[fengints]

it also fails with jdsp4linux. Problem is not in easyeffects, its somewhere else

[fengints]

Running under bash: problem gone.

[fengints]

similar problems, in their case they solved it by upgrading ram or increasing swap file. What i observed, it gets down by fish when memory usage starts growing, even if there is still a space

https://github.com/bes-dev/stable_diffusion.openvino/issues/8 https://github.com/orgs/community/discussions/29281

[wwmm]

getting the same, problem with fish ? Running under bash: problem gone.

Interesting. Through the years I have seen some users having crashes while using fish. But I never thought about asking them to try bash.

[wwmm]

It is not OOM who kills it, there is no logs + ram is free enough.

In the beginning I thought that the the OOM was involved in the cases where EasyEffects is being killed but in none of those cases memory usage was a problem. I wish whatever is killing the process gave a clear message about the reasons why this is being done.