Skip to content

Unplugging external monitor leads to gnome-shell crash #257

@bkuczenski

Description

@bkuczenski

Hi, this is a re-opening of #238 with some more information.
Environment: Arch linux, current Gnome desktop (44.3). use of this extension in 2x3 arrangement, with an external monitor connected via USB-C to VGA. Intel i915 laptop display.

When I unplug the external monitor, with roughly 1/6 odds, I will get a syslog event including the following:

Aug 09 15:56:57 glyph gnome-shell[39000]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Aug 09 15:56:57 glyph gnome-shell[39000]: == Stack trace for context 0x55c5c3310440 ==
Aug 09 15:56:57 glyph gnome-shell[39000]: The offending signal was window-entered-monitor on MetaDisplay 0x55c5c3682b00.

window-left-monitor also appears as a signal.

The above 3 messages are repeated endlessly until the crash state is resolved. The computer is unusable while the event is ongoing. killing gnome-shell resolves the crash- though sometimes it recovers on its own e.g by tty-switching. This crash generated 10.8MB of log output (57k lines) during 1s of crash state.

It is 100% correlated with use of this extension.
How can I help solve this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions