Long VC sessions cause renderer to crash

Aknowledgements

• 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.

• I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself. I have tested if this bug occurs on Chromium/Chrome or any other Chromium-based browser that uses unpatched/upstream Chromium engine.

• 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.

• 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

21.0.1

Application version

3.8.6

Bug description

After spending around an hour in a voice channel, WebCord’s webview/renderer goes blank and the program locks up (except the system tray bar menu.) In such a state, I cannot bring up the toolbar, nor the Developer Tools.

I tried tweaking the settings in various ways but still got the same results, always forcing me to restart the app.

I also don’t see any odd output from the program, even with the verbose runtime flag.

I’m using Arch + i3wm with WebCord AppImage (I also tried out webcord-bin AUR package, although I know it’s not official.)

Screenshot

Additional context

Notice: This issue was automatically generated by WebCord.

[dolwup]

I experience the same issue on Arch + Gnome Wayland on AMD. I wanted to add that this also happens on chromium (106.0.5249.91) with the discord website. The only difference is that Chromium doesn’t out right freeze, it just displays the “Oh no! The Tab crashed” page. So this might not be necessarily your bug.

[SpacingBat3]

I have a long vc tomorrow so I’ll run it with those flags and send the logs through if it freezes up. I assume it will save the logs to the directory where the command is run, if not where?

You probably want to provide it into the --log-file param value (e.g. --log-file=./electron_logs.txt), forgot to mention that.