Maximizing "accept invitation" window crashes the whole program about webcord

[SpacingBat3]

Resizing the window doesn't crash, but opening it in a tiling window manager like e.g. Hyprland might.

It doesn't crash for me on XFCE4+Nouveau (with XFWM4, which is floating window manager) everything works as it should be (no crash, maximize works fine). I see you could reproduce this on KDE/Wayland (I suppose?); which package are you using to run WebCord and does it tweak OZONE to launch WebCord within Wayland as opposed to Chromium defaults (i.e. most likely XWayland)? Also, can you reproduce this with X11 DE (check this on something else than XWayland)?

You might try checking how it works with Wayland if you're at XWayland and the opposite way.

[SpacingBat3]

(...) which it doesn't do on the official Discord client which I also have installed, so that's a plus for WebCord! (...)

That could actually be due to WebCord starting its own WebSocket server at the same port as Discord, overriding it (meaning browsers might not access Discord if WebCord's running). You might try starting Discord first and waiting for it to fully load, then starting WebCord in order to have Discord reserve port number before WebCord (or just avoid running Discord in general when WebCord's already running).

[Lampe2020]

That could actually be due to WebCord starting its own WebSocket server

Before I had WebCord installed and discord-canary from Discord's official deb file was running in the background basically whenever my computer was turned on it didn't open the invite window either.

[Lampe2020]

which package are you using to run WebCord

I'm using the […]amd64.deb from the releases/latest page of this repo.

does it tweak OZONE to launch WebCord within Wayland as opposed to Chromium defaults (i.e. most likely XWayland)?

I have absolutely no clue. I just installed the package as stated above and ran it.

You might try checking how it works with Wayland if you're at XWayland and the opposite way.

How do I see how the internal Chromium instance is launched? I think it should run in Wayland directly, but I don't know what Electron version you use and if that required XWayland to run.

I see you could reproduce this on KDE/Wayland (I suppose?);

Well, the bug stopped reliably happening; as soon as I changed my /proc/sys/kernel/core_pattern to capture the core dump to a file instead of a pipe to apport the bug became unreliable and now only happens sometimes.