thread 'main' has overflowed its stack

[JustSimplyKyle]

thread 'main' has overflowed its stack

[JakeStanger]

Hey, please share your log file and any error messages spat out in the console as I've nothing to go on otherwise

[JustSimplyKyle]

runtime log: https://c-v.sh/beetlepaction.txt
error.log:
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Run with RUST_BACKTRACE=full to include source snippets.
2023-07-22T05:38:59.172092Z WARN ironbar::ipc::server: Socket already exists. Did Ironbar exit abruptly?
2023-07-22T05:38:59.172101Z WARN ironbar::ipc::server: Attempting IPC shutdown to allow binding to address
2023-07-22T05:40:50.581117Z ERROR ironbar:
0: EOF while parsing a value at line 1 column 0

Location:
src/ipc/client.rs:25

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
2023-07-22T05:40:50.581255Z ERROR ironbar:
0: Connection reset by peer (os error 104)

Location:
src/ipc/client.rs:23

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

[JakeStanger]

It looks like you're running an old git version from the log. Can you make sure you're on the latest commit first please?

Also I can see it is absolutely spamming IPC requests and image reloads. Are you constantly sending commands to the server with no pause?

[JakeStanger]

So quick update to this. I've just installed NixOS because my Arch install seems to be imploding and figured it'd be something different for a while. My config immediately hit the same crash, but the default config takes a few minutes.

We'll need to whittle this down, but there's a something somewhere that's causing weird behaviour on Nix.

[JustSimplyKyle]

hmm, I'm not using nixos nor nix.
The latest git seems to have fixed it? but more testing needs to be done.(Is there a way to make ironbar open as default config?)
Also about the spamming IPC requests stuff
The speed interval is 100ms, I don't think it's that insane.
https://asciinema.org/a/gMiBf9ihffYJNiSnlCpYHx6pq

[JakeStanger]

That is much higher CPU and memory usage than I'd expect to see, but yeah 100ms is not insane. I wonder what's going on, since it was fine for me on Arch.

[JakeStanger]

An update: I ran with IRONBAR_LOG=trace and I can see the desktop files cache mutex is getting absolutely absolutely spammed, so something is causing the desktop file icon loading code to run way more than it should