[GH-ISSUE #1102] New scripts get spawned on each config reload #1751

New issue

Closed

opened 2026-05-22 22:54:30 +01:00 by JakeStanger · 1 comment

JakeStanger commented

2026-05-22 22:54:30 +01:00

Owner

Originally created by @postsolar on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1102

Describe the bug

New scripts get spawned on each ironbar reload.

To reproduce
Steps to reproduce the behavior:

Add module script

For example:

    {
      "cmd": "tail -f /dev/null",
      "mode": "watch",
      "type": "script"
    }

Issue an ironbar reload a few times
Observe there are many child processes instead of just one

Expected behavior

Either reuse the previous instance upon reload and don't create new ones, or kill it before spawning the new one.

System information:

Distro: NixOS
Compositor: Hyprland
Ironbar version: 106e23e311

Configuration

Config

{
  "center": [
    {
      "cmd": "tail -f /dev/null",
      "mode": "watch",
      "type": "script"
    }
  ]
}

Styles

Additional context

Screenshots

Originally created by @postsolar on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1102 **Describe the bug**  New scripts get spawned on each ironbar reload. **To reproduce** Steps to reproduce the behavior: 1. Add module `script` For example: ```json { "cmd": "tail -f /dev/null", "mode": "watch", "type": "script" } ``` 3. Issue an `ironbar reload` a few times 4. Observe there are many child processes instead of just one **Expected behavior**  Either reuse the previous instance upon reload and don't create new ones, or kill it before spawning the new one. **System information:** - Distro: NixOS - Compositor: Hyprland - Ironbar version: 106e23e3116db02d57c548820024163c38491370 **Configuration**  <details><summary>Config</summary> ```json { "center": [ { "cmd": "tail -f /dev/null", "mode": "watch", "type": "script" } ] } ``` </details> <details><summary>Styles</summary> ```css ``` </details> **Additional context**  **Screenshots**  <img width="402" height="268" alt="Image" src="https://github.com/user-attachments/assets/565bb160-7732-410b-83ed-14aa8e253c07" />

JakeStanger

2026-05-22 22:54:30 +01:00

closed this issue
added the
P:Medium

T:Bug

A:Core
labels

JakeStanger commented

2026-05-22 22:54:31 +01:00

Author

Owner

@JakeStanger commented on GitHub (Aug 4, 2025):

I suspect the play here is that running script handles need to be stored somewhere (possibly just against the Ironbar global), and some sort of reload signal needs to be sent that kills all the processes.

Re-attaching might be possible but trickier, as a config reload means it won't be a 1:1 mapping between processes. I guess if processes were hashed against their command it wouldn't be difficult to diff them.

@JakeStanger commented on GitHub (Aug 4, 2025): I suspect the play here is that running script handles need to be stored somewhere (possibly just against the Ironbar global), and some sort of reload signal needs to be sent that kills all the processes. Re-attaching might be possible but trickier, as a config reload means it won't be a 1:1 mapping between processes. I guess if processes were hashed against their command it wouldn't be difficult to diff them.