EasyEffect crashes with Chrome #2625
Comments
|
The log attached is of a normal run. There is no crash there. So it will be hard to figure out what is going on. |
Is there any other debugging method ? It just randomly crashes. Sometimes it works fine, but crashes most of the time. |
No. But even if there was it would not help if the crash does not happen while running in debug mode. What is in the output of @MeowIce is there anything suspicious in the output of |
The Debug Log``` Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1377 Remote error message: unknown resource 156 op:2 Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1376 Remote error res: No such file or directory Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1377 Remote error message: unknown resource 156 op:2 Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1376 Remote error res: No such file or directory Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1377 Remote error message: unknown resource 156 op:2 Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1376 Remote error res: No such file or directory Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1377 Remote error message: unknown resource 53 op:2 Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1376 Remote error res: No such file or directory Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1377 Remote error message: unknown resource 53 op:2 Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1376 Remote error res: No such file or directory Sep 28 20:29:32 meowpc easyeffects[19488]: pipe_manager.cpp:1377 Remote error message: unknown resource 53 op:2 Sep 28 20:29:32 meowpc easyeffects[19488]: stream_output_effects.cpp:297 link from node 122 to output device 128 failed Sep 28 20:29:33 meowpc easyeffects[19488]: stream_output_effects.cpp:297 link from node 122 to output device 128 failed Sep 28 20:29:33 meowpc easyeffects[19488]: stream_output_effects.cpp:297 link from node 122 to output device 128 failed Sep 28 20:29:33 meowpc easyeffects[19488]: stream_output_effects.cpp:297 link from node 122 to output device 128 failed Sep 28 20:29:33 meowpc pipewire[1376]: pw.node: driver easyeffects_sink did not update duration/rate (1024/256 48000/48000) Sep 28 20:29:33 meowpc easyeffects[19488]: stream_output_effects.cpp:297 link from node 122 to output device 128 failed Sep 28 20:29:33 meowpc easyeffects[19488]: stream_output_effects.cpp:297 link from node 122 to output device 128 failed Sep 28 20:29:33 meowpc audit[19488]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=19488 comm="easyeffects" exe="/app/bin/easyeffects" sig=11 res=1 Sep 28 20:29:33 meowpc kernel: easyeffects[19488]: segfault at 29 ip 000055a69ccba1f4 sp 00007ffc6d89e948 error 4 in easyeffects[55a69cc47000+364000] likely on CPU 1 (core 1, socket 0) Sep 28 20:29:38 meowpc systemd-coredump[19982]: Process 19488 (easyeffects) of user 1000 dumped core. #0 0x000055a69ccba1f4 n/a (/app/bin/easyeffects + 0xa71f4) #1 0x000055a69cf9bb5f n/a (/app/bin/easyeffects + 0x388b5f) #6 0x000055a69cc6e68a n/a (/app/bin/easyeffects + 0x5b68a) #9 0x000055a69cc71785 n/a (/app/bin/easyeffects + 0x5e785) Sep 28 20:29:38 meowpc systemd[1212]: dbus-:1.2-com.github.wwmm.easyeffects@8.service: Main process exited, code=exited, status=139/n/a Sep 28 20:29:38 meowpc systemd[1212]: dbus-:1.2-com.github.wwmm.easyeffects@8.service: Failed with result 'exit-code'. Sep 28 20:29:38 meowpc systemd[1212]: app-flatpak-com.github.wwmm.easyeffects-19474.scope: Consumed 27.204s CPU time. Sep 28 20:29:45 meowpc abrt-notification[20056]: Process 19488 (easyeffects) crashed in ??() ``` |
|
Coredump: |
|
Coredump from the system won’t work well with flatpak crashes, as you can see it gets confused with symbols. Try https://github.com/wwmm/easyeffects/wiki/Reporting-Bugs#with-flatpak |
It is not something that usually happens but I do not remember it leading to crashes...
Hmm... I wonder why... |
This what the debug is ? |
Honestly I am not sure about how it is possible we could be crashing at this location. In any case I have updated our master branch with some small changes that may help to avoid it. After sometime a Flatpak package built from our master branch should be available here https://github.com/wwmm/easyeffects/actions/runs/6341917875. |
I've installed your flatpak devel build, but it refused to start |
Should be fixed in #2628. |
|
I still have the crashing issue with the Devel build journalctlSep 29 15:37:20 meowpc rtkit-daemon[774]: Successfully made thread 44193 of process 44162 (/app/bin/easyeffects) owned by '1000' RT at priority 20. Sep 29 15:38:34 meowpc easyeffects[44162]: convolver.cpp:276 soe: convolver: irs file does not exists or it is empty: /home/meowice/.var/app/com.github.wwmm.easyeffects/config/easyeffects/irs/XHR StudioMaster HD.irs Sep 29 15:38:34 meowpc easyeffects[44162]: convolver.cpp:277 soe: convolver: Entering passthrough mode... Sep 29 15:39:24 meowpc easyeffects[44162]: convolver.cpp:276 soe: convolver: irs file does not exists or it is empty: /home/meowice/.var/app/com.github.wwmm.easyeffects/config/easyeffects/irs/XHR StudioMaster HD.irs Sep 29 15:39:24 meowpc easyeffects[44162]: convolver.cpp:277 soe: convolver: Entering passthrough mode... Sep 29 15:40:45 meowpc plasmashell[1487]: org.kde.klipper: Invalid or non-local url for preview: QUrl("com.github.wwmm.easyeffects") Sep 29 15:41:19 meowpc systemd[1212]: Started dbus-:1.2-com.github.wwmm.easyeffects.Devel@0.service. Sep 29 15:41:19 meowpc systemd[1212]: Started app-flatpak-com.github.wwmm.easyeffects.Devel-44712.scope. Sep 29 15:41:20 meowpc rtkit-daemon[774]: Successfully made thread 44748 of process 44730 (/app/bin/easyeffects) owned by '1000' RT at priority 20. Sep 29 15:41:57 meowpc systemd[1212]: dbus-:1.2-com.github.wwmm.easyeffects.Devel@0.service: Main process exited, code=exited, status=137/n/a Sep 29 15:41:57 meowpc systemd[1212]: dbus-:1.2-com.github.wwmm.easyeffects.Devel@0.service: Failed with result 'exit-code'. Sep 29 15:41:57 meowpc systemd[1212]: app-flatpak-com.github.wwmm.easyeffects.Devel-44712.scope: Consumed 4.942s CPU time. coredumpctl
flatpak coredump--Type for more, q to quit, c to continue without paging--c Core was generated by `/app/bin/easyeffects --gapplication-service'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000055e54aa0b1ff in ui::chart::get_is_visible (self=0x55e54f31e7f0) at ../src/chart.cpp:175 175 return (self->data != nullptr) ? self->data->is_visible : false; [Current thread is 1 (Thread 0x7f02b0577300 (LWP 2))] simplescreenrecorder-2023-09-29_15.51.52.mp4 |
Somehow this is not the right binary. As it can be seen here 4670532 the line where the crash happened isn't like that anymore. |
|
Make sure you are running |
Oops ! I posted the wrong dump xD |
There was progress after the last update. Based on the core dump EasyEffects does not seem to be crashing anymore. Its execution was aborted because something generated the |
The question is which one. Without the core dump pointing a direction it will be hard to figure it out. But at least it shows that EasyEffects code isn't crashing anymore. Maybe a system update or reboot may have some effect. |
I killed the normal EE earlier, but idk why the Devel is also counted in the coredump. Full cd: flatpak coredump[meowice@meowpc ~]$ flatpak-coredumpctl com.github.wwmm.easyeffects.Devel Executable /chrome_crashpad_handler doesn't seem to be a flatpaked application. Running: `"flatpak" "run" "--filesystem=home" "--filesystem=/tmp" "--command=gdb" "--devel" "com.github.wwmm.easyeffects.Devel" "/chrome_crashpad_handler" "/tmp/tmpf918r36v"` F: Not sharing "/usr/share/icons" with sandbox: Path "/usr" is reserved by Flatpak GNU gdb (GDB) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". warning: Can't open file /chrome_crashpad_handler during file-backed mapping note processing warning: Can't open file /usr/lib64/libc.so.6 during file-backed mapping note processing warning: Can't open file /usr/lib64/libgcc_s-13-20230728.so.1 during file-backed mapping note processing warning: Can't open file /usr/lib64/libm.so.6 during file-backed mapping note processing warning: Can't open file /usr/lib64/libpthread.so.0 during file-backed mapping note processing warning: Can't open file /usr/lib64/libdl.so.2 during file-backed mapping note processing This GDB supports auto-downloading debuginfo from the following URLs: And EE Devel still crashes |
|
Sometimes it crashes upon start-up. ABRT has saved the report. |
So now the signal is SIGBUS... I wonder what is different on Fedora. This problem is too easy to reproduce on your system to be just a problem in EasyEffects code. Otherwise people on other distributions would also be reporting constant crashes. |
I have no idea why either. This time it threw a SIGSERV |
|
@MeowIce do you notice the crash with other plugins besides the convolver and the crystalizer? These two plugin are based on the |
You're right. Another unknown issue is, EasyEffects crashes while disconnecting my Bluetooth headphones (put them to my case). It also happens when connecting. |
simplescreenrecorder-2023-10-01_14.45.01.mp4 |
Hmm... Many years ago there was a mysterious random crash that only happened when the crystalizer and the convolver plugins were used at the same time. But the coredump messages were very clear about the problem being calls to the zita-convolver library. It seemed that for some reason this library did not like the idea of having multiple instances of itself running at the same time. As the years went by the bug somehow fixed itself and I was never able to reproduce it again. Maybe what you are seeing right now is some variant of it. But honestly I hope that the source of yours problem is something else. If the issue is in the zita-convolver library fixing it is beyond my reach. |
Do you have any idea about EE crashing upon connecting/reconnecting bluetooth devices/headphone shown in the above ? |
Does it happen when there is no plugin in the pipeline or the global bypass in EasyEffects top bar is active? Or only when the convolver and the crystalizer plugins are enabled? Switching output devices forces some filter links to be recreated. IF the convolver and the crystalizer have to be active the two crashes probably have the same source. Whatever it is. But if it happens even without plugins in the pipeline then something totally different is taking effect. |
Yes.
I've disabled all effects/filters/plugins (whatever it's called) but still crashes
Maybe xD |
Hmm... I think in Fedora's repositories there is an EasyEffects package. Maybe from an older version but it will be interesting to know if it is also having crashes. |
I don't have crashing issue with rpm package from Fedora's repo upon changing BT devices. Looks like it only happens with flatpak package. |
Hmm... And what is the version of the Fedora's package? |
7.1.0 |
Then it seems to be Flatpak issue. Though I have no idea how. Maybe some weird incompatibility between the runtime versions used in Flatpak and Fedora @vchernin ? |
No idea what could cause this. There is a flatpak runtime update which I will do soon, maybe it will somehow improve things. |
EasyEffects Version
7.1.0
What package are you using?
Flatpak (Flathub)
Distribution
Fedora 38
Describe the bug
Whenever I'm watching YouTube on Chrome. When the video reaches any section without sound (the speaker icon on the tab disappears), EasyEffect crashes.
Expected Behavior
EasyEffects won't crash
Debug Log
Debug Log
Additional Information
No response
The text was updated successfully, but these errors were encountered: