Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-3298GitHub issuePublicReceived

Walker memory usage grows each time launching an app with walker.

Reported by nganaremba-rem · filed Oct 13, 2025Closed upstream on 2025-10-14 by its own reporter nganaremba-rem, as a duplicate of #698 (R-2484). GitHub close reason: duplicate.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Walker memory usage grows each time launching an app with walker.revision 1 · captured 2026-10-04 11:42 UTC via poll

System details

Omarchy v3.0.2, Arch Linux

What's wrong?

Bug

When starting Walker with --gapplication-service, memory usage grows each time I launch an app and never goes down. After some usage, it easily exceeds 1.2 GB (seen in btop).

Steps

  1. Autostart Walker with:
exec-once = walker --gapplication-service
  1. Launch apps repeatedly via Walker.
  1. Observe memory in btop → keeps increasing, never released.

Expected
Memory should remain stable.

Workaround
Using a systemd user service with a memory cap fixes the issue:

[Service]
ExecStart=/usr/bin/walker --gapplication-service
Restart=on-failure
MemoryMax=300M

And launching via:

exec = systemctl --user start walker.service; walker -p "Start…"

Request
Please investigate the memory leak in --gapplication-service.

View raw text
### System details

Omarchy v3.0.2, Arch Linux

### What's wrong?

### Bug

When starting Walker with --gapplication-service, memory usage grows each time I launch an app and never goes down. After some usage, it easily exceeds 1.2 GB (seen in btop).

**Steps**

1. Autostart Walker with:
```
exec-once = walker --gapplication-service
```

2. Launch apps repeatedly via Walker.

3. Observe memory in btop → keeps increasing, never released.

**Expected**
Memory should remain stable.

**Workaround**
Using a systemd user service with a memory cap fixes the issue:
```
[Service]
ExecStart=/usr/bin/walker --gapplication-service
Restart=on-failure
MemoryMax=300M
```

And launching via:
```
exec = systemctl --user start walker.service; walker -p "Start…"
```

**Request**
Please investigate the memory leak in --gapplication-service.

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.