Guilty GL_CONTEXT_LOST crash loop!

[Fuzzyzilla]

Hyprland Version

System/Version info

```sh Hyprland, built from branch HEAD at commit 03ebbe18ed8517ee22591eac82cd54322f42cb7d (props: bump ver to 0.34.0). Date: Mon Jan 1 12:03:15 2024 Tag: v0.34.0 flags: (if any) ```

I am a fresh install of Arch, using the most recent hyprland package. Graphics drivers are Mesa 23.3.3, on a VEGA 8 iGPU

Bug or Regression?

Bug

Description

Intermittently, the desktop and all apps visually freeze and stop interacting. Upon this happening, a sort of roulette occurs:

• After about 15s, one OpenGL app is killed (sometimes hyprland itself) and things go back to normal
• After about 15s, I regain mouse and keyboard control but things remain visually frozen until I logout with Super+M or switch to TTY. The session is irrecoverable and switching back to it results in the same crash loop.
• The system never recovers and I must use the powerswitch

The reason I am posting this here instead of attributing it to a general graphics bug in my system is the inclusion of

[wlr] [render/gles2/pass.c:258] GPU reset (guilty)

in the logs throughout the crash loop.

How to reproduce

Unfortunately I have not determined a pattern in when/why/which of these crashes I experience, which has made it difficult to report full information. There is no correlation between how many/which apps are open, time between crashes, or graphical load - it has even crashed in this way with no windows shortly after boot (eww and hyprpaper would be the only clients there on my setup)

It occurs regardless of if hyprland is launched through a login manager or TTY.

Crash reports, logs, images, videos

Crash loop begins after 5,600 lines. In this case, the crash was one where I was able to regain mouse+keyboard control but unable to interact. Towards the end of the log (after line 31,900), I was able to switch to a TTY, destroying the GL context and ending the crash loop. Not included in the log is me switching back to that session, which started the crash loop once more.

These events do not trigger a crash log. Apologies for the 1.6 MB of the same string repeated! hyprland.log glxinfo (Device: AMD Radeon Vega 8 Graphics) glxinfo.txt

[Fuzzyzilla]

Using a different graphics device has fixed the issue. I am still left unsure whether it's an issue with the limits/capabilities of Vega8 not being enough for Hyprland, a driver bug, or a hardware issue. Increasing the memory of the Vega8 has not yet helped, but breaking the 1GiB mark makes it less worthwhile for me to use it anyway as it then consumes a substantial portion of my system memory.