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.
Wayland layer surfaces allocate VRAM even when not visible
Reported by derekszen · filed Jan 15, 2026Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
Core Issue: Wayland Layer Surfaces Always Allocate VRAM
Walker (app launcher) uses 131MB VRAM even when never invoked. Why?
The Problem
Wayland layer surfaces like app launchers allocate VRAM on startup and keep it allocated even when never visible.
Current VRAM Usage:
- walker: 131 MiB (never invoked, just running as daemon)
- hiddify: 415 MiB
- firefox: 845 MiB
What we tried (doesnt work):
- render_unfocused_fps = 1 (only affects windows, not layer surfaces)
- vfr = true (doesnt stop allocation, just rendering)
The Real Question:
Is this VRAM allocation:
1. Wayland protocol requirement?
2. Hyprland implementation that could be optimized?
3. App-specific (walker should unmap when hidden)?
4. Working as intended?
What we need from Omarchy:
- Documentation explaining the behavior
- Whether this can be made truly on-demand
- Configuration options if available
This is about Wayland layer surface behavior, not NVIDIA setup
View raw text
## Core Issue: Wayland Layer Surfaces Always Allocate VRAM **Walker (app launcher) uses 131MB VRAM even when never invoked. Why?** ### The Problem Wayland layer surfaces like app launchers allocate VRAM on startup and keep it allocated even when never visible. ### Current VRAM Usage: - walker: 131 MiB (never invoked, just running as daemon) - hiddify: 415 MiB - firefox: 845 MiB ### What we tried (doesnt work): - render_unfocused_fps = 1 (only affects windows, not layer surfaces) - vfr = true (doesnt stop allocation, just rendering) ### The Real Question: Is this VRAM allocation: 1. Wayland protocol requirement? 2. Hyprland implementation that could be optimized? 3. App-specific (walker should unmap when hidden)? 4. Working as intended? ### What we need from Omarchy: - Documentation explaining the behavior - Whether this can be made truly on-demand - Configuration options if available **This is about Wayland layer surface behavior, not NVIDIA setup**
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.