Open zaps166 opened 21 hours ago
Happens often, but not always (at least one effect must be enabled).
I am doing some tests and it does not happen when no audio is passing through EasyEffects. Only after something is playing audio to it that the issue happens. Really odd...
Using the Quit
entry in our menus works fine. What is not entirely surprising considering that this and ctrl+Q
make sure that app quits. Something unexpected is happening when just closing the window.
0x00007ffff7f279c5 in pw_thread_loop_lock () at /usr/lib/libpipewire-0.3.so.0
Hum... This is a sign that somewhere a lock done to the pipewire's loop could not be followed by the corresponding unlock call.
Thanks for investigation! Indeed the Ctrl+Q works correctly!
EasyEffects Version
7.2.1
What package are you using?
Arch (easyeffects)
Distribution
Manjaro
Describe the bug
Closing EasyEffects window (Shutdown on Window Closing option is enabled) stops audio processing and closes the window, but
easyeffects
process keeps running and eats RAM. Happens often, but not always (at least one effect must be enabled).Expected Behavior
easyeffects
process closes.Debug Log
On debugger I can notice hang/SIGSEGV/SIGABRT on close. Here is SIGABRT with Equalizer effect as example.
Debug Log (easyeffects-debug-7.2.1 package)
``` #0 0x00007ffff5ca53f4 in ??? () at /usr/lib/libc.so.6 #1 0x00007ffff5c4c120 in raise () at /usr/lib/libc.so.6 #2 0x00007ffff5c334c3 in abort () at /usr/lib/libc.so.6 #3 0x00007ffff5c34354 in ??? () at /usr/lib/libc.so.6 #4 0x00007ffff5c43fa6 in ??? () at /usr/lib/libc.so.6 #5 0x00007ffff5ca69da in ??? () at /usr/lib/libc.so.6 #6 0x00007ffff7f31d08 in ??? () at /usr/lib/libpipewire-0.3.so.0 #7 0x00007ffff7f279c5 in pw_thread_loop_lock () at /usr/lib/libpipewire-0.3.so.0 #8 0x0000555555840bd5 in PipeManager::lock (this=
Additional Information
EasyEffects and PipeWire from Arch/Manjaro official repositories. Issue happens for longer while.