electron: [Bug]: SIGSEGV crash when maximizing window

Preflight Checklist

Electron Version

30.0.0-alpha7

What operating system are you using?

Ubuntu

Operating System Version

20.04, running on x11

What arch are you using?

x64

Last Known Working Electron version

30.0.0-alpha6

Expected Behavior

Maximizing/fullscreening the app does not sigfault.

Actual Behavior

Maximizing/fullscreening the window crashes the app.

Testcase Gist URL

This is visible in the default Fiddle template that opens with the app

Additional Information

There is no render-process-gone or child-process-gone event called when it crashes.

About this issue

  • Original URL
  • State: open
  • Created 3 months ago
  • Reactions: 21
  • Comments: 24 (13 by maintainers)

Most upvoted comments

temporary workaround for anyone experiencing this: launch vesktop with

electron29 /usr/lib/vesktop/app.asar

(note: requires, obviously, electron29 to be installed)

To avoid confusion and better help devs find this issue, I’m editing the title & original post to be about maximizing rather than fullscreen

I can confirm that 30.0.2 also exhibits this issue. We have multiple users complaining about segfaults on launch across various distributions (Arch, Fedora, Debian). Some report that they have a window tiling manager that will also crash on a few older versions of Electron. I personally just tested this out with Manjaro and Plasma, and I can observe that the main window is being drawn properly, but not maximized. However, the app will call maximize immediately after window creation. But the window never actually maximizes, indicating that it is indeed the maximizing step that causes the core dump. Possibly also an interaction with tiling managers, so I think there may be a wider issue that in general relates to how window operations are handled.

EDIT: The bug seems to not appear on the current 29er line Electron version (29.3.2) and that one runs fine for all users who reported segfaults before.

Crashing here (Ubuntu) as well since I upgraded to version 30.0.1 from ~29. I see the same SIGSEGV issue.

The issue persists in 30.0.1 as well as 31.0.0-alpha.1 and 31.0.0-alpha.2.