[BUG] Clicking on desktop notification crashes the app

[vega-d]

Aknowledgements

• [X] I have checked that there's no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.

• [X] I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself.

• [X] I have tried running the build from the master branch and it does not have any fixes implemented according to my issue.

• [ ] My issue describes one of the unstable and/or not fully implemented features.

• [X] I have found a workaround to mitigate or temporarily fix this issue (please write it in Additional context section).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

18.2.4

Application version

v3.1.4

Bug description

Clicking on the desktop notification about a mention crashes the app.

1. turn on "Enable Desktop Notifications" in discord settings
2. get a mention
3. click on the notification.
4. the app dies.

log:

ega@dart ~/Downloads [1]> webcord 
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[1077788:0530/114333.330003:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[WebSocket] Listening at port 6463.
[UPDATE] New application version is available! (v3.1.4 → v3.2.0)
[1077788:0530/114410.606077:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
fish: Job 1, 'webcord' terminated by signal SIGTRAP (Trace or breakpoint trap)

Additional context

Disabling notifications stops it from crashing, but then there are obviously no notifications...

[SpacingBat3]

Try to update to WebCord 3.2.0 to see if this occurs on Electron 19 as well...

[vega-d]

I can confirm it's on 3.2.0 too.

[SpacingBat3]

Since my client doesn't really handle Discord notifications, I can only guess it is an Electron issue. I still couldn't reproduce it on other notifications, through...

[Etaash-mathamsetty]

I don't even get notifications lmao (even on chrome)

[Etaash-mathamsetty]

ok can confirm I am now getting notifications on chrome but not on webcord, so my notification system is setup correctly. any help with this?

[SpacingBat3]

ok can confirm I am now getting notifications on chrome but not on webcord, so my notification system is setup correctly. any help with this?

Unrelated with issue #134, maybe start a discussion or new issue? I want to keep threads clean, which means comments should be related to the current topic, in this example – notifications crash.

[SpacingBat3]

Can't reproduce this issue, even on Electron 18.2.4. No crash occurs, WebCord just switches me to the related chat / DM. I'll flag this as wontfix for now...

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = > (null)
[1077788:0530/114333.330003:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.

One of these lines might be relevant to what could cause a crash – something's definitely wrong within Chromium engine and the way it uses GPU driver.

Also, what's your DE? If it is on Wayland, it might be a reason why I can't reproduce it – it is still quite complicated how Chromium and Electron works on Wayland and in some cases I've read/heard it might even crash without any reason.

[vega-d]

Also, what's your DE?

I'm using latest gnome 42 with wayland on intel XE graphics. Silverblue 36.

[SpacingBat3]

I believe this issue is stale, as a lot has changed in terms of the Electron. I will close it but if you have any thoughts or want to confirm it still occurs on WebCord 3.7.0+, you can reply to me there and I will re-open this issue.