JakeStanger/ironbar

Fork 0

mirror of https://github.com/JakeStanger/ironbar.git synced 2026-07-11 08:15:21 +01:00

[GH-ISSUE #453] Error log file grows indefinitely & can result in very large files #4369

New issue

Closed

opened 2026-05-23 00:52:52 +01:00 by JakeStanger · 5 comments

JakeStanger commented

2026-05-23 00:52:52 +01:00

Owner

Originally created by @JakeStanger on GitHub (Feb 13, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/453

Discussed in https://github.com/JakeStanger/ironbar/discussions/451

how the hell did the error log get up to 282.6 GiB
^{Originally posted by **pinkcreeper100** February 13, 2024}
https://akko.wtf/notice/AeqeKmpXN9P9D6N54i

it was full of broken pipe errors

Originally created by @JakeStanger on GitHub (Feb 13, 2024). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/453 ### Discussed in https://github.com/JakeStanger/ironbar/discussions/451 <div type='discussions-op-text'> <b>how the hell did the error log get up to 282.6 GiB</b><br> <sup>Originally posted by **pinkcreeper100** February 13, 2024</sup><br> https://akko.wtf/notice/AeqeKmpXN9P9D6N54i it was full of broken pipe errors</div>

JakeStanger

2026-05-23 00:52:52 +01:00

closed this issue
added the
T:Bug
label

JakeStanger commented

2026-05-23 00:52:53 +01:00

Author

Owner

@aquifolly commented on GitHub (Mar 2, 2024):

@JakeStanger
the original cause is still occurring though

2024-03-01T07:36:14.772167Z ERROR ironbar::clients::wayland: 
   0: Failed to dispatch pending wayland events
   1: other error during loop operation
   2: underlying IO error
   3: Broken pipe (os error 32)

Location:
   src/clients/wayland/mod.rs:305

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

@aquifolly commented on GitHub (Mar 2, 2024): @JakeStanger the original cause is still occurring though ``` 2024-03-01T07:36:14.772167Z ERROR ironbar::clients::wayland: 0: Failed to dispatch pending wayland events 1: other error during loop operation 2: underlying IO error 3: Broken pipe (os error 32) Location: src/clients/wayland/mod.rs:305 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. Run with RUST_BACKTRACE=full to include source snippets. ```

JakeStanger commented

2026-05-23 00:52:53 +01:00

Author

Owner

@JakeStanger commented on GitHub (Mar 2, 2024):

Please open a proper issue with more detail and I can investigate

@JakeStanger commented on GitHub (Mar 2, 2024): Please open a proper issue with more detail and I can investigate

JakeStanger commented

2026-05-23 00:52:53 +01:00

Author

Owner

@ToxicMushroom commented on GitHub (Jun 12, 2024):

This may be related to incorrectly launching ironbar #632 ?

Every 2.0s: ls -al .local/share/ironbar/ironbar.2024-06-12.log             arch: Wed Jun 12 02:44:42 2024

-rw-r--r-- 1 merlijn merlijn 24266396770 Jun 12 02:44 .local/share/ironbar/ironbar.2024-06-12.log

700MB in about 1 minute

Every 2.0s: ls -al .local/share/ironbar/ironbar.2024-06-12.log             arch: Wed Jun 12 02:45:50 2024

-rw-r--r-- 1 merlijn merlijn 24926470338 Jun 12 02:45 .local/share/ironbar/ironbar.2024-06-12.log

Apparently I have many ironbar processes running

130 merlijn@arch ~ % pgrep ironbar
2809
188396
374343
374381
399618
399683

Every time I reload sway it creates another ironbar that is just producing these errors in a loop x)

I think ideally ironbar should detect that it is already running and not try to do whatever it is doing right now ? Or maybe there is a way to handle sway reload better.

@ToxicMushroom commented on GitHub (Jun 12, 2024): This may be related to incorrectly launching ironbar #632 ? ``` Every 2.0s: ls -al .local/share/ironbar/ironbar.2024-06-12.log arch: Wed Jun 12 02:44:42 2024 -rw-r--r-- 1 merlijn merlijn 24266396770 Jun 12 02:44 .local/share/ironbar/ironbar.2024-06-12.log ``` 700MB in about 1 minute ``` Every 2.0s: ls -al .local/share/ironbar/ironbar.2024-06-12.log arch: Wed Jun 12 02:45:50 2024 -rw-r--r-- 1 merlijn merlijn 24926470338 Jun 12 02:45 .local/share/ironbar/ironbar.2024-06-12.log ``` Apparently I have many ironbar processes running ``` 130 merlijn@arch ~ % pgrep ironbar 2809 188396 374343 374381 399618 399683 ``` Every time I reload sway it creates another ironbar that is just producing these errors in a loop x) ![image](https://github.com/JakeStanger/ironbar/assets/32853531/10d4e8b1-bea1-464c-bdb1-3d9b4d6165ab) I think ideally ironbar should detect that it is already running and not try to do whatever it is doing right now ? Or maybe there is a way to handle sway reload better.

JakeStanger commented

2026-05-23 00:52:53 +01:00

Author

Owner

@ToxicMushroom commented on GitHub (Jun 12, 2024):

Might be useful to know that it's the old process that starts freaking out, not the newly created one after reload

@ToxicMushroom commented on GitHub (Jun 12, 2024): Might be useful to know that it's the old process that starts freaking out, not the newly created one after reload

JakeStanger commented

2026-05-23 00:52:53 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jun 13, 2024):

I think ideally ironbar should detect that it is already running and not try to do whatever it is doing right now ? Or maybe there is a way to handle sway reload better.

It's supposed to exit if another instance is already running, so this is a separate bug. The additional instances shouldn't get any further than setting up a Wayland client though, so that likely wouldn't explain the config file sizes.

@JakeStanger commented on GitHub (Jun 13, 2024): > I think ideally ironbar should detect that it is already running and not try to do whatever it is doing right now ? Or maybe there is a way to handle sway reload better. It's *supposed* to exit if another instance is already running, so this is a separate bug. The additional instances shouldn't get any further than setting up a Wayland client though, so that likely wouldn't explain the config file sizes.