Crash when Dis/Reconnecting a monitor while a client is using ext-workspace

[EvilLary]

Description

Disconnecting a monitor and reconnecting it again while a client is using ext-workspace crashes Hyprland. Waybar or any small wayland program binding ext-workspace is enough to reproduce the crash.

Steps to reproduce

• Launch any client using ext-workspace, e.g. waybar (below is an example waybar config)
• Disconnect your monitor
• Reconnect it

Waybar config

{
    "height": 30,
    "spacing": 4,
    "modules-center": [
        "ext/workspaces"
    ],
    "ext/workspaces": {}
}

Regression

I don't know, I've tried going back to as far as when ext-workspace was added to Hyprland 3bbdf9d , but It's stil crashes on me

Logs

asan.log.12731.txt

Not the same process as asan
backtrace.log
hyprlandCrashReport17042.txt
hyprlandd.log
hyprlandd.conf.txt

[vaxerski]

yeah cuz @outfoxxed is stupid, let me fix this rq. Thanks for the asan log.

[vaxerski]

fixed 79a2781

[EvilLary]

Unfortunately it still crashes if you unplug all monitors and plug them back again.

This works

• Unplug montior 1 and plug it back in
• Monitor 2 stays on

I couldn't get an asan log, I've tried make asan and running the the commands manually but no asan.log was generated

backtrace.txt
hyprlandd.log
hyprlandCrashReport117.txt

And a small note Hyprland makes a "virtual monitor" if I could call it that on another graphical session (kwin wayland), even though it was launched in an another tty (same user). So this might make you unable to reproduce the crash.

Tested Sway and launched from different tty, and it deson't create a "virtual monitor" on KDE plasma.
I don't know if it's my setup or something else

Edit: Seems to only happen with KDE

[vaxerski]

patch.txt
try this>?

[EvilLary]

It works now. Thanks!