"webcord killed by SIGSEGV" on Linux Fedora 38

philam commented 1 year ago

Acknowledgements

[X] I have checked that there is no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
[ ] This bug affects Discord website.
[ ] This issue is confirmed to be reproducible when WebCord is packaged on at least all three latest supported Electron major releases.
[ ] This issue is reproducible in Chrome, Chromium or any Chromium-based browser, e.g Brave or Edge (please write in Additional Context which browser you have used if it is neither Chrome nor unmodified Chromium).
[x] There are no fixes done to master which resolves this issue.
[ ] My issue describes one of the unstable and/or not fully implemented features.
[ ] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

v26.0.0

Application version

v4.4.0

Bug description

After a few seconds of loading, I get a "this app crashed" notification and the Webcord window goes blank. The application stays open but blank.

Unsure if it's related to #452 because I get error information that is different:

webcord killed by SIGSEGV

This happens on both X11 and Wayland.

Screenshot below

Screenshot_20230825_091006

Additional context

System specs:

Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS

acv-98 commented 1 year ago

Same problem here on Fedora 38 Wayland (ASUS laptop)

Likely crash reason: Jump to an invalid address Exploitable rating (0-9 scale): 6 reason: webcord killed by SIGSEGV

~I believe switching to x11 instead of Wayland makes it work again, but not the best fix~ -- no longer works actually

tydog98 commented 1 year ago

Also getting this, using the Flatpak version.

EDIT: I think this is a duplicate of the other issue, downgrading the Flatpak fixed it.

ypossem commented 11 months ago

I am not certain it's the same issue (the graphics bug), it might be a different issue also introduced with Electron 26. 4.4.1 was supposed to detect a crash loop and then engage safe mode. What I'm seeing, is about 5-10 render crashes, followed by the entire application packing up. If that isn't the issue you meant, then please be more specific about which issue you think it is duplicating. I'm on X11 myself (XFCE).

But yes, I'm doing the flatpak downgrade flatpak update --commit=a35defd55a5da112609c61babd223c9f05aa198b1338cdbee0f72974e467765c io.github.spacingbat3.webcord

SpacingBat3 commented 11 months ago

I am not certain it's the same issue (the graphics bug), it might be a different issue also introduced with Electron 26. 4.4.1 was supposed to detect a crash loop and then engage safe mode. What I'm seeing, is about 5-10 render crashes, followed by the entire application packing up. If that isn't the issue you meant, then please be more specific about which issue you think it is duplicating. I'm on X11 myself (XFCE).

But yes, I'm doing the flatpak downgrade flatpak update --commit=a35defd55a5da112609c61babd223c9f05aa198b1338cdbee0f72974e467765c io.github.spacingbat3.webcord

I'm certain that's just the description of #452, both of these issues end up with the same outcome (crashed renderer) and the WebCord will take similar steps in order to approach the recover from the crash (10x page reload, then approach to switch to safe mode by restarting app with --safe-mode flag), however since WebCord adds argv[0] which is usually path to Electron binary, Electron or WebCord might wrongly interpret the cmdline if it doesn't relaunch automatically in 4.4.1, although from my tests adding gibberish to WebCord's cmdline shouldn't break anything.

Also safe mode is not guaranteed to fix every kind of crash, although it should mitigate crashes if those are caused by issues with GPU acceleration, some WebCord tweaks made to Chromium command-line or problems with the buggy driver. This doesn't seem to be the case for this issue, so I have no clue if I could workaround it in any other way than upgrading/downgrading Electron version.

Anyway, I suppose I'll close this issue ticket in favour of #452. Any conversation should be continued there.

SpacingBat3 / WebCord