Crash with Maximizer and Autogain together

[ParticleMon]

EasyEffects Version

7.16 distro, 7.19 Flatpak

What package are you using?

Other (specify below)

Distribution

Linux Mint 22

Describe the bug

An eventual crash seems to occur most likely by having at least Maximizer and Autogain enabled simultaneously.

Although a console message is typically not displayed after a crash (is there a secret debug switch?), once the included debug log was displayed (newlines subsequently removed):

My current effects chain includes effects always enabled and effects occasionally enabled, the latter indicated by brackets: Equalizer, Bass Enhancer, [Bass Enhancer], [Loudness], [Maximizer], [Autogain], [Exciter], [Filter], Stereo Tools, [Limiter].

I most often enable Maximizer and Autogain together, usually leaving the rest disabled. Crashes seem to occur with streaming video quicker than with streaming audio. This is as close as I have as yet been able to replicate the issue.

Due to my distro having an old version, I have been using the Flatpak.

Expected Behavior

No response

Debug Log

Debug Log

(easyeffects:2): easyeffects-WARNING **: 10:46:51.998: 	pipe_manager.cpp:1511	Remote error res: No such file or directory
(easyeffects:2): easyeffects-WARNING **: 10:46:51.998: 	pipe_manager.cpp:1512	Remote error message: unknown resource 64 op:2
(easyeffects:2): easyeffects-WARNING **: 10:46:51.998: 	pipe_manager.cpp:1511	Remote error res: No such file or directory
(easyeffects:2): easyeffects-WARNING **: 10:46:51.998: 	pipe_manager.cpp:1512	Remote error message: unknown resource 64 op:2
(easyeffects:2): easyeffects-WARNING **: 10:46:51.998: 	pipe_manager.cpp:1511	Remote error res: No such file or directory
(easyeffects:2): easyeffects-WARNING **: 10:46:51.998: 	pipe_manager.cpp:1512	Remote error message: unknown resource 64 op:2
(easyeffects:2): easyeffects-WARNING **: 10:46:51.999: 	pipe_manager.cpp:1511	Remote error res: No such file or directory
(easyeffects:2): easyeffects-WARNING **: 10:46:51.999: 	pipe_manager.cpp:1512	Remote error message: unknown resource 64 op:2
(easyeffects:2): easyeffects-WARNING **: 10:46:51.999: 	pipe_manager.cpp:1511	Remote error res: No such file or directory
(easyeffects:2): easyeffects-WARNING **: 10:46:51.999: 	pipe_manager.cpp:1512	Remote error message: unknown resource 64 op:2
(easyeffects:2): easyeffects-WARNING **: 10:46:51.999: 	pipe_manager.cpp:1511	Remote error res: No such file or directory
(easyeffects:2): easyeffects-WARNING **: 10:46:51.999: 	pipe_manager.cpp:1512	Remote error message: unknown resource 64 op:2

Additional Information

No response

[violetmage]

Can you provide the full debug log, from program start to crash? It's difficult to understand the full context with just the information one provided.

[ParticleMon]

That is the full log--there typically isn't any log. So, if there's a an argument or parameter for verbose debug output, do tell.

[violetmage]

To get debug logs for easyeffects on a flatpak installation, you'll need to run easyeffects from the command line like this:
flatpak run --env=G_MESSAGES_DEBUG=easyeffects com.github.wwmm.easyeffects

Before running this command, remember to shutdown any open instance of easyeffects using the Quit button in the app menu (three horizontal lines in the top right of easyeffects, popup menu).

[ParticleMon]

Thanks. (Quit sure is easier than killing the process in System Monitor.)

This log captures the simultaneous streaming of a video, playing a local mp4, and streaming a radio station (not my normal workflow), which crashed after several seconds.

Then, with Maximizer and Autogain disabled, playing these sources worked without issue for minutes, after which adding the filters crashed after several seconds.

debug.txt

[wwmm]

I did not notice anything unusual in the logs. @ParticleMon try to see if in the output of sudo journalctl there is anything related to the crash. Like a killed message. Sometimes what happens isn't a crash in the usual meaning of the word but the system killing the process for some reason.

I use the autogain the the maximizer everyday without issues. So the system killing EasyEffects feels more likely than the plugins actually crashing.