System reports high IO pressure when Ghostty is running

Since switching to Ghostty, my system has been reporting extreme IO pressure.

> cat /proc/pressure/io
some avg10=97.74 avg60=86.94 avg300=88.00 total=186275074182
full avg10=94.75 avg60=84.19 avg300=84.31 total=180228532605

I've narrowed it down to Ghostty's app cgroup:

> cat /sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/app.slice/app-ghostty-transient-470209.scope/app/io.pressure
some avg10=98.21 avg60=85.35 avg300=33.56 total=121725763
full avg10=98.02 avg60=85.10 avg300=33.46 total=121378879

Also see https://github.com/ghostty-org/ghostty/discussions/3224 for similar reports.

It seems the io_uring backend is buggy and we should build with epoll. The mentioned configuration option isn't released yet.

ghostty 1.1.2-1

(reports itself as 1.1.2-arch; I think the version string should be set to "$pkgver-arch$pkgrel", not just "$pkgver-arch")

added priority3-normal severity4-low statusunconfirmed labels

assigned to @freswa, @alerque, @toolybird, and @gromit

changed title from Ghostty "causes" high IOwait: to System reports high IO pressure when Ghostty is running

mentioned in commit fae959f9

mentioned in merge request !4 (merged)

added scopebug statusconfirmed labels and removed statusunconfirmed label

assigned to @orhun and @ptr1337 and unassigned @freswa, @toolybird, and @gromit

closed with commit fae959f9

closed with merge request !4 (merged)