Walker instance is not being killed on keybind

[crqch]

System details

Intel(R) Core(TM) i7-8700K (12) @ 4.80 GHz, NVIDIA GeForce GTX 1070 Ti, Omarchy v3.0.1

What's wrong?

When a walker menu is already open, press a shortcut that opens the same or other walker menu. The previous instance is not killed, so the previous items remain as new ones appear in the same picker.

2025-09-22.14-34-49.mov

[rossvz]

I think this also may be causing a memory leak for walker.

• Open btop (Super+T by default)
• Spam the walker keybind (Super+Space) - hit this a few dozen times
• Watch the walker memory usage climb and never drop

[Furyfree]

I can confirm this issue. Walker’s memory usage keeps climbing over time, even when idle. If the system isn’t restarted frequently, Walker will continue consuming more and more RAM until it’s either killed manually or the computer is rebooted.

[Furyfree]

Suggestion is to bump the walker version to the newest as walker seems to have fixed it in newer versions

[ryanrhughes]

Resolved via #1005