Hyperlock crashes every 40ish minutes with SIGSEGV

[devopsmerc]

Regression?

Yes, it started March 11th. which is when i ran omarchy update

Hyprlock Info and Version

hyprlock version: 0.9.3-2

Hyprlock config

source = ~/.config/omarchy/current/theme/hyprlock.conf

general {
    ignore_empty_input = true
}

background {
    monitor =
    color = $color
    path = ~/.config/omarchy/current/background
    blur_passes = 3
}

animations {
    enabled = false
}

input-field {
    monitor =
    size = 650, 100
    position = 0, 0
    halign = center
    valign = center

    inner_color = $inner_color
    outer_color = $outer_color
    outline_thickness = 4

    font_family = JetBrainsMono Nerd Font
    font_color = $font_color

    placeholder_text = Enter Password
    check_color = $check_color
    fail_text = <i>$FAIL ($ATTEMPTS)</i>

    rounding = 0
    shadow_passes = 0
    fade_on_empty = false
}

auth {
    fingerprint:enabled = false
}

Compositor Info and Version

System/Version info

Hyprland 0.54.3 built from branch v0.54.3 at commit 521ece463c4a9d3d128670688a34756805a4328f clean (version: bump to 0.54.3).
Date: Fri Mar 27 18:17:50 2026
Tag: v0.54.3, commits: 7014

Libraries:
Hyprgraphics: built against 0.5.0, system has 0.5.0
Hyprutils: built against 0.12.0, system has 0.12.0
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.10.0, system has 0.10.0

Version ABI string: 521ece463c4a9d3d128670688a34756805a4328f_aq_0.10_hu_0.12_hg_0.5_hc_0.1_hlg_0.6
no flags were set


System Information:
System name: Linux
Node name: ksp2om
Release: 6.19.10-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Thu, 26 Mar 2026 19:20:28 +0000

Libraries:
Hyprgraphics: built against 0.5.0, system has 0.5.0
Hyprutils: built against 0.12.0, system has 0.12.0
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.10.0, system has 0.10.0



GPU information:
08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA102 [GeForce RTX 3070 Ti] [10de:2207] (rev a1) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  595.58.03  Release Build  (root@ksp2om)


os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo


plugins:

Explicit sync: supported
GL ver: 3.2
Backend: drm

Monitor info:
        Panel HDMI-A-1: 3440x1440, HDMI-A-1 Microstep MSI MAG341CQ MA0H058500136 -> backend drm
                explicit ✔️
                edid:
                        hdr ❌
                        chroma ✔️
                        bt2020 ❌
                vrr capable ❌
                non-desktop ❌

        Panel DP-1: 2560x1440, DP-1 Samsung Electric Company Odyssey G5 HNAX600925 -> backend drm
                explicit ✔️
                edid:
                        hdr ✔️
                        chroma ✔️
                        bt2020 ✔️
                vrr capable ❌
                non-desktop ❌

Description

hyprlock has been crashing repeatedly approximately every 40 minutes since March 11, 2026. Over 110 crashes have been recorded. The application terminates with both SIGABRT and SIGSEGV signals, with stack traces indicating threading/synchronization deadlocks.

Claude came up with the count and rough time, but its pretty obvious. I tried to get claude to find a way to reproduce the issue but didnt have any luck. Seems to only be time but that can't be the only way. I'll continue to try to find something more helpful.

How to reproduce

Lock the screen and wait 40-60 minutes and it crashes every time. If wake it after 30 minutes I can keep it running but any longer and it crashes.

Crash reports, logs, images, videos

Crash Details:

• Signal types: SIGABRT (abort) and SIGSEGV (segmentation fault)
• Frequency: ~40-60 minute intervals (100+ crashes in ~3.5 weeks)
• First occurrence: March 11, 2026
• Status: Ongoing as of April 15, 2026

Stack Trace (Most Recent - SIGABRT):
Process 16168 (hyprlock) of user 1000 dumped core on Signal 6 (ABRT)
Timestamp: Tue 2026-04-14 23:13:08 CDT

Main thread abort() call stack:
#0 0x00007f4837ca7a2c in libc.so.6
#1 0x00007f4837c4d1a0 raise() in libc.so.6
#2 0x00007f4837c345fe abort() in libc.so.6
#3 0x0000557c85f9ea2f in hyprlock
#4 0x0000557c85fe71c8 in hyprlock
#5 0x0000557c8601f808 in hyprlock
#6-11 Wayland protocol dispatch

Blocked threads show deadlock patterns:

• Thread 16178: pthread_cond_clockwait in libhyprgraphics.so.4 (asyncAssetSpinLock)
• Thread 16179: pthread_cond_wait on condition variable
• Thread 16184: pthread_mutex_lock
• Thread 16183: pthread_cond_clockwait
• Thread 16185: g_cond_wait in libglib (pangoft2)

[devopsmerc]

Looks like it started with 0.9.3 version and it probably related to #961 and #988. I'll check to see if 0.9.4 hits the arch repo tomorrow to see if that fixes it. Sorry that i didn't notice this sooner.

[PointerDilemma]

I would like hyprlock not to crash. But it's very hard to understand what's going like this.
Logs Please?

#2 0x00007f4837c345fe abort() in libc.so.6

This might be a runtime assert firing, but it's probably not a deadlock.

[PointerDilemma]

Ok so the backtrace is almost useless. But not quite.
I downloaded archlinux 0.6.3-2 binary and checked it out in ghidra so see if I can find an executable address ending with 0xa2f that calls abort.

And indeed there is and the call to abort comes from wl_egl_create_window. So #988 might be a band aid. That failure means either monitor x or y is 0, or that an allocation failed. Probably the first is the case, but maybe there is a memory leak (although I doubt that, since your config is so simple and it should rarely render a frame)

Let me know if it also happens with 0.6.4.

[devopsmerc]

the logs didn't really have anything useful at all. I updated it to use --verbose so hopefully we'll get something useful in the next 30-50 minutes.

[devopsmerc]

It crashed as expected final few log messages below. I just installed 9.4 so I'll find out of that helped.

[TRACE] GPU Reports supported format 30334241 with modifier 300000000606015 [TRACE] GPU Reports supported format 30334241 with modifier 300000000e08010 [TRACE] GPU Reports supported format 30334241 with modifier 3000wl_display#1: error 0: invalid object 26

[PointerDilemma]

Chack latest git, if you can. Maybe this is similar to #991.