Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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.
Opening a select menu walks its rows quadratically (omacom/omarchy#10601)
Low-severity issue, currently open.
What this means for you
Plain-language impact — what this issue could mean for your users and your system, before any of the technical detail.
Opening a long select menu does work that grows with the square of its length, because the menu measures the whole list again after each row is added. Menus of tens of rows open without a visible delay, but the 231-row keybindings menu (Super+K) costs 27,027 row visits each time it opens. Nothing breaks; the menu only opens more slowly.
Technical description
rebuildDmenuDisplay (shell/plugins/menu/Menu.qml) appends rows to displayModel one at a time. The visibleRowsHeight binding evaluates again after each append. Each pass calls foldedListHeight over the full row list.
A menu of N rows thus costs about N(N+1)/2 row visits. 231 rows take 232 height passes and 27,027 row visits. 462 rows take 463 passes and 107,415 visits.
The Super+K keybindings menu is the realistic large case. Upstream issue: omacom/omarchy#10601. Report intake validated it (report cmulr8ysi0jwr1gw4fjmt9khq). Upstream PR 10631 does not change the counts.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Performance
- CVE surface
- None
Where it is
The code the issue lives in — peek the affected function inline to see it in context.
- Menu.qml rebuildDmenuDisplay + visibleRowsHeight binding (omarchy-menu-select summon)
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
sh test/reports/report-cmulr8ysi0jwr1gw4fjmt9khq.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
sh test/reports/report-cmulr8ysi0jwr1gw4fjmt9khq.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Menus of typical size (tens of rows) open without a visible delay. The cost grows only for very long select lists such as the keybindings menu
The fix
Append the rows in one model update, or defer the height binding until the rebuild ends. Also add a requirement that bounds the menu-open cost; none exists today
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
No authoredcode links reach these requirements in this historical reconstruction. Automatically derived code links aren't reconstructible for past runs, so implementing code may have existed without an authored trace.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- proof/evidence/ki-menu-open-quadratic.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.