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.
omarchy-network-speedtest leaves orphaned curl workers running against fast.com after the panel is closed
Reported by londospark · filed Sep 7, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8515 (R-1389). GitHub close reason: completed.
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
Title: omarchy-network-speedtest leaves orphaned curl workers running against fast.com after the panel is closed
What happened
Opening the network speed test panel (and/or letting its dials finish/dismissing it)
does not stop the underlying traffic. omarchy-network-speedtest spawns 8 parallel
background workers, each looping curl requests against fast.com/Netflix OCA
endpoints indefinitely until told to stop. When the Quickshell panel closes, it setsProcess.running = false on its child, which sends the script a plain SIGTERM.
The script only registers trap cleanup EXIT (/usr/bin/omarchy-network-speedtest,
around line 67). Bash's EXIT trap fires on a normal/caught exit path, but an
untrapped SIGTERM uses the kernel's default disposition and kills the process
immediately — the EXIT trap never runs, so cleanup() (which is supposed topkill/kill/wait the 8 background workers) never executes. All 8 worker
subshells are orphaned, get reparented, and keep running their while true curl
loops forever, continuously downloading/uploading against Netflix's CDN and
saturating the connection.
Observed directly: after closing/finishing a speed test, `pgrep -fa
omarchy-network-speedtest` showed 7 still-running instances of the script, each with
a live curl child mid-transfer against *.oca.nflxvideo.net, sustaining ~600 Mbps
of unwanted download traffic minutes after the test should have ended.
Expected
Closing the speed test panel (or the phase timer completing) should terminate all
background workers and their curl children within a second or two, with no lingering
network traffic.
Fix
Register the cleanup trap for TERM/INT as well as EXIT:
-trap cleanup EXIT
+trap cleanup EXIT TERM INTThis was applied locally as a workaround; it should be fixed upstream so it survivesomarchy update.
System
- Omarchy version: 4.0.2-mac.1 (Asahi/Apple Silicon fork)
- File: /usr/bin/omarchy-network-speedtest (symlinked from
/usr/share/omarchy/bin/omarchy-network-speedtest)
View raw text
Title: omarchy-network-speedtest leaves orphaned curl workers running against fast.com after the panel is closed ## What happened Opening the network speed test panel (and/or letting its dials finish/dismissing it) does not stop the underlying traffic. `omarchy-network-speedtest` spawns 8 parallel background workers, each looping `curl` requests against fast.com/Netflix OCA endpoints indefinitely until told to stop. When the Quickshell panel closes, it sets `Process.running = false` on its child, which sends the script a plain SIGTERM. The script only registers `trap cleanup EXIT` (`/usr/bin/omarchy-network-speedtest`, around line 67). Bash's `EXIT` trap fires on a normal/caught exit path, but an untrapped `SIGTERM` uses the kernel's default disposition and kills the process immediately — the `EXIT` trap never runs, so `cleanup()` (which is supposed to `pkill`/`kill`/`wait` the 8 background workers) never executes. All 8 worker subshells are orphaned, get reparented, and keep running their `while true` curl loops forever, continuously downloading/uploading against Netflix's CDN and saturating the connection. Observed directly: after closing/finishing a speed test, `pgrep -fa omarchy-network-speedtest` showed 7 still-running instances of the script, each with a live `curl` child mid-transfer against `*.oca.nflxvideo.net`, sustaining ~600 Mbps of unwanted download traffic minutes after the test should have ended. ## Expected Closing the speed test panel (or the phase timer completing) should terminate all background workers and their curl children within a second or two, with no lingering network traffic. ## Fix Register the cleanup trap for `TERM`/`INT` as well as `EXIT`: ```diff -trap cleanup EXIT +trap cleanup EXIT TERM INT ``` This was applied locally as a workaround; it should be fixed upstream so it survives `omarchy update`. ## System - Omarchy version: 4.0.2-mac.1 (Asahi/Apple Silicon fork) - File: /usr/bin/omarchy-network-speedtest (symlinked from /usr/share/omarchy/bin/omarchy-network-speedtest)
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.