mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 11:15:20 +01:00
[GH-ISSUE #250] thread 'main' has overflowed its stack #5734
Labels
No labels
A:Build
A:CI
A:Client
A:Config
A:Core
A:Documentation
A:Documentation
A:IPC
A:Testing
A:UX/UI
blocked
BREAKING CHANGE
duplicate
good first issue
GTK4
help wanted
invalid
M:Battery
M:Battery
M:Bindmode
M:Bluetooth
M:Brightness
M:Cairo
M:Clipboard
M:Clock
M:Clock
M:Custom
M:Focused
M:Keyboard
M:Launcher
M:Menu
M:Music
M:Music
M:Music
M:Network Manager
M:Notifications
M:SysInfo
M:Tray
M:Volume
M:Workspaces
partially resolved
P:Critical
P:High
P:Low
P:Medium
pull-request
T:Bug
T:Bug
T:Core Enhancement
T:Module Enhancement
T:New Module
T:Question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/ironbar#5734
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JustSimplyKyle on GitHub (Jul 21, 2023).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/250
Describe the bug
ironbar crashes
To Reproduce
Steps to reproduce the behavior:
I'm not sure...
my guess maybe css's errors too much?(I don't use
pxin my config)but for me, running it for around 5 min would trigger the crash
System information:
Configuration
Config
Styles
Additional context
it could also be the newly added ipc?
and the memory usage seems to be consistently going up till it crashes
@JakeStanger commented on GitHub (Jul 21, 2023):
Hey, please share your log file and any error messages spat out in the console as I've nothing to go on otherwise
@JustSimplyKyle commented on GitHub (Jul 22, 2023):
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 commented on GitHub (Jul 22, 2023):
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 commented on GitHub (Jul 23, 2023):
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 commented on GitHub (Jul 23, 2023):
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 commented on GitHub (Jul 23, 2023):
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 commented on GitHub (Jul 24, 2023):
An update: I ran with
IRONBAR_LOG=traceand 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