google chrome crashes when moving window between monitors

[ogabriel]

Description

Whenever I drag or move a Chrome window between two monitors under Hyprland, it closes instantly without warning.

this was something that was reported on the issues too by other person: #11957

I upgraded my packages today on archlinux, restarted the PC and this started to happen

what I tested up till now

1. tested other applications, like firefox, obsidian, discord etc. this happens to none of them, only chrome
2. sometimes moving window between monitors work
   1. if my vertical monitor on the right has a terminal (alacritty) opened, if I move any window there, it does not crash, but as soon as I close the terminal and try to move it again, it can crash again if I move windows
   2. but there is a cool caveat, if I click/hover on the "tab" part of the chrome window on the monitor that has the terminal, chrome crashes

chrome error

[388055:388055:1007/181832.471721:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: wl_display#1: error 0: invalid object 60

[1007/181832.482563:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[1007/181832.483567:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
zsh: trace trap (core dumped)  google-chrome-stable --no-crashpad --disable-crash-reporter

jornalctl

 systemd-coredump[388432]: [🡕] Process 388055 (chrome) of user 1000 dumped core.

system info

OS: Arch Linux x86_64
Kernel: Linux 6.16.10-arch1-1
Display (DELL S2425H): 1080x1920 in 24", 100 Hz [External]
Display (DEL41DB): 2560x1440 in 27", 144 Hz [External]
WM: Hyprland 0.51.1 (Wayland)
CPU: AMD Ryzen 7 PRO 4750U (16) @ 1.70 GHz
GPU: AMD Radeon Vega Series / Radeon Vega Mobile Series [Integrated]
Memory: 8.10 GiB / 14.49 GiB (56%)

hyprctl version

Hyprland 0.51.1 built from branch  at commit 71a1216abcc7031776630a6d88f105605c4dc1c9  ([gha] Nix: update inputs).
Date: Mon Sep 22 20:54:03 2025
Tag: v0.51.1, commits: 6436
built against:
 aquamarine 0.9.4
 hyprlang 0.6.3
 hyprutils 0.9.0
 hyprcursor 0.1.13
 hyprgraphics 0.2.0


no flags were set

[ItsOhen]

Chrome recently started trying to use wayland color management.
Try running it with --disable-features=WaylandWpColorManagerV1, and wait for next hl tag/release.

[gwimbly03]

worked thanks

[niklasw]

Thanks!

[transporsche]

thank you very much!

[vandaimer]

Amazing! Working.

[fortitudepub]

Amazing, thanks god, this save my life.

I was just trying to find some way to capture why chromium crash, at first I do not think it's crash until I just do some ps after the drag.

[hyperair]

See #11843

[luffyxxsenpai]

same issue with brave, so i guess it will be replicated for all the chromium based browsers

[CraigBurden]

Can confirm the same issue with the latest 141.0.7390.107 Google Chrome release

[erdnuesse]

Addition:
For anyone using flatpak (user installs, not system) and want to use a custom-flags.conf file, the full path to the file is:
~/.var/app/<your-chromium-browser-fork-of-choice>/config/chromium-flags.conf

Also: in brave for example, the filename has to be brave-flags.conf, for either native or flatpak installs; the separate folder rule still applies.