Arch Linux

[chromium] crash on wayland when creating new window on monitors with different scaling

Description:

Assume a sway setup with two monitors, each with different scaling factors. One monitor will now become "afflicted"; when attempting to launch chromium with that monitor focused (eg: running `chromium` on an xterm on monitor 1), chromium will launch, create a window, and immediately crash with the following logs:

```
$ chromium --user-data-dir=$(mktemp -d)
[15233:15233:0408/122327.921960:ERROR:wayland_event_watcher.cc(38)] libwayland: xdg_wm_base@15: error 4: wrong configure serial: 13347

[0408/122327.930374:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1] 15233 trace trap (core dumped) chromium --user-data-dir=$(mktemp -d)
```

This makes it impossible to start chromium on that monitor. More annoyingly, accidentally running "chromium" on that monitor will cause all other windows to crash, due to them sharing the same underlying chromium instance.

- I have not noticed any pattern in terms of _which_ monitor causes chromium to crash; it can switch after restarting sway. But one monitor is always afflicted, and any window created on it will always cause chromium to crash. Chromium seems to work normally on the "healthy" monitor.
- If I start chromium on the "healthy" monitor, move the window to the "afflicted" monitor, then create a new window (via control-shift-n), then chromium will crash.
- Sometimes, the chromium window will persist for a second or two on the affected monitor before crashing.

Core dump backtraces, `about:gpu` info, and package dependency versions are all attached.


Package Versions:

chromium 111.0.5563.64-2, sway 1.8.1. Version numbers of chromium's dependencies are attached.

Hardware:

One high-DPI monitor 3840x2160 with scale 3, one 1920x1080 monitor with scale 1. Error manifests only when using different scaling factors.
Running on an Intel i7 CPU+GPU.

Relevant Issues+Links:

- I'm unable to reproduce this with the official chromium builds, which leads me to believe it's an Arch specific issue.
- NixOS users are having a similar issue at https://github.com/NixOS/nixpkgs/issues/225277 , and have bisected their issue to commit de134a1 (110.0.5481.177 -> 111.0.5563.64). The issue may be sway-specific?
- Relevant chromium upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1430657

Steps to reproduce:

Start sway with two monitors. Give them different scaling factors (eg: `output eDP-1 scale 3`). Launch chromium on one monitor (eg: run ` chromium --user-data-dir=$(mktemp -d)` in an xterm on that monitor). Repeat a few times. chromium will segfault, and all windows will exit. If no error occurs, try the same process on the other monitor, and chromium will segfault.