gnome-shell crashes on Wayland when dragging a hardware-accelerated Chrome tab to an external monitor on hybrid graphics (AMD/NVIDIA)

Component: mutter

Versions:

    OS: Fedora Workstation 43 (Development Branch)

    GNOME Shell: 49.0-1.fc43

    Mutter: 49.0-1.fc43

    NVIDIA Driver: 580.82.09

    Kernel: 6.17.0-0.rc6.49.fc43.x86_64

    Google Chrome: 140.0.7339.185

Hardware:

    Model: Razer Blade 14 (2025)

    Integrated GPU: AMD Radeon 890M

    Dedicated GPU: NVIDIA GeForce RTX 5070 Max-Q / Mobile

Steps to Reproduce:

    On a system with the hardware and software above, log into a GNOME Wayland session.

    Connect an external monitor via HDMI.

    Open Google Chrome with hardware acceleration enabled (chrome://settings -> "Use graphics acceleration when available").

    Open any website.

    Click and drag a tab to detach it into a new window.

    Drag the newly created window onto the external monitor.

Expected Results:
The Chrome window moves to the external monitor seamlessly.

Actual Results:
The entire gnome-shell process crashes, terminating the user session and returning to the GDM login screen. The crash is reproducible.

Supporting Logs:

The journal from the previous boot (journalctl -b -1) shows a core dump from gnome-shell. The stack trace clearly indicates a crash in mutter during the window dragging operation:

Sep 26 11:25:54 fedora systemd-coredump[15698]: [🡕] Process 3238 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 3238:
#0  0x00007f4eda8c6114 meta_window_get_display (libmutter-17.so.0 + 0xc6114)
#1  0x00007f4eda891618 meta_window_drag_end (libmutter-17.so.0 + 0x91618)
#2  0x00007f4eda93db3b meta_wayland_toplevel_drag_end (libmutter-17.so.0 + 0x13db3b)
#3  0x00007f4eda91fce3 drag_grab_release (libmutter-17.so.0 + 0x11fce3)
#4  0x00007f4eda929428 meta_wayland_input_handle_event (libmutter-17.so.0 + 0x129428)

Additionally, the kernel log contains repeated PCIe power state errors which may or may not be related:

Sep 26 09:53:45 fedora kernel: pcieport 0000:02:04.0: Unable to change power state from D3hot to D0, device inaccessible

Workaround:
Disabling hardware acceleration in Google Chrome prevents the crash.