When closing RuneLite (https://runelite.net), an unofficial client for
Old School RuneScape, if the included GPU plugin was enabled, the client
will freeze and hang instead of closing normally. I've experienced this
since Debian 12, and encountered the same behavior when I was using an
AMD 6650 XT GPU, as I do now with an AMD 7800 XT GPU. This behavior does
not occur when the GPU plugin is disabled. In this frozen state, the
client does not respond to input of any kind and must be SIGKILLed to be
closed fully.

In this state, I've attached gdb to the running Java process, and
attached the logs from running `thread apply all bt`. Based on those
logs, I'm reasonably confident this is a GPU driver bug as Thread 2
(RuneLite Shutdown) is waiting on Thread 66 (Java VM Thread), which is
stuck after several libgallium calls which have no debug symbols. I'm
happy to provide any further logs which might be helpful, as I can
reproduce this every time the program is closed.

Thanks!

On Sun, 31 Aug 2025 15:43:40 -0700 Jordan Atwood  <nightfirecat@nightfirec.at> wrote:
 > Package: mesa-libgallium
 > Version: 25.0.7-2
 > Severity: normal

I've now updated my system to Debian testing, per the below output,
which includes mesa-libgallium 25.2.2-1. Unfortunately, I'm still
experiencing the same hang as before the upgrade.

```
$ lsb_release -dc
Description:    Debian GNU/Linux forky/sid
Codename:       forky
```

Hi,

In the time since my last reply, I have reported this bug upstream to
mesa[1], where it was quickly found to be a deadlock in the particular
graphics library framework used in RuneLite, namely LWGJL, with certain
JDKs.[2] They have landed a change in their latest version which I'm
happy to report fixes the deadlocks I was experiencing. Just wanted to
bring that info back here to close the loop on this.

[1]: https://gitlab.freedesktop.org/mesa/mesa/-/work_items/16015
[2]: https://github.com/LWJGL/lwjgl3/issues/1140