Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Runaway memory leak in quickshell causing system-wide OOM
Reported by austrasien · filed Sep 2, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Description
On Omarchy v4.0.2-1, the quickshell process (PID 1459) experienced an extreme, runaway memory allocation/leak, consuming over 43.5 GB of resident memory (anon-rss) and 167 GB of virtual memory (total-vm).
This completely exhausted all physical RAM (46 GB) and system swap space (98 GB), bringing the system to a critical Out of Memory (OOM) state. As a result, other user processes—such as the Cursor IDE (Electron)—crashed via internal allocator traps (SIGTRAP) due to allocation failure, before the kernel's OOM-killer ultimately stepped in and terminated quickshell to rescue the system.
Evidence (Kernel Logs)
Sep 02 23:38:06 omarchy kernel: electron invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=200
...
Sep 02 23:38:06 omarchy kernel: [ pid ] uid tgid total_vm rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name
...
Sep 02 23:38:06 omarchy kernel: [ 1459] 1000 1459 41788245 10896991 10896987 4 0 278638592 23707501 200 quickshell
...
Sep 02 23:38:06 omarchy kernel: Out of memory: Killed process 1459 (quickshell) total-vm:167152980kB, anon-rss:43587948kB, file-rss:16kB, shmem-rss:0kB, UID:1000 pgtables:272108kB oom_score_adj:200System Details
- Omarchy Version: 4.0.2-1
- Kernel: 7.1.9-arch1-2 (PREEMPT)
- Hardware: Framework Laptop 13 (AMD Ryzen AI 300 Series) / BIOS 04.02
Filed by Gemini CLI via interactive agent.
View raw text
### Description On Omarchy v4.0.2-1, the `quickshell` process (PID 1459) experienced an extreme, runaway memory allocation/leak, consuming over **43.5 GB of resident memory (anon-rss)** and **167 GB of virtual memory (total-vm)**. This completely exhausted all physical RAM (46 GB) and system swap space (98 GB), bringing the system to a critical Out of Memory (OOM) state. As a result, other user processes—such as the Cursor IDE (Electron)—crashed via internal allocator traps (`SIGTRAP`) due to allocation failure, before the kernel's OOM-killer ultimately stepped in and terminated `quickshell` to rescue the system. ### Evidence (Kernel Logs) ```text Sep 02 23:38:06 omarchy kernel: electron invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=200 ... Sep 02 23:38:06 omarchy kernel: [ pid ] uid tgid total_vm rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name ... Sep 02 23:38:06 omarchy kernel: [ 1459] 1000 1459 41788245 10896991 10896987 4 0 278638592 23707501 200 quickshell ... Sep 02 23:38:06 omarchy kernel: Out of memory: Killed process 1459 (quickshell) total-vm:167152980kB, anon-rss:43587948kB, file-rss:16kB, shmem-rss:0kB, UID:1000 pgtables:272108kB oom_score_adj:200 ``` ### System Details * **Omarchy Version:** 4.0.2-1 * **Kernel:** 7.1.9-arch1-2 (PREEMPT) * **Hardware:** Framework Laptop 13 (AMD Ryzen AI 300 Series) / BIOS 04.02 --- Filed by Gemini CLI via interactive agent.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.