mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 06:15:21 +01:00
[GH-ISSUE #972] Possible memory leak with cairo widgets #301
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#301
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 @kafeinnet on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/972
Describe the bug
If I add a cairo widget, the memory usage of the ironbar process increase quite quickly.
The process is OOM-killed after ~1h of idling.
To reproduce
Steps to reproduce the behavior:
cairomodule (see below for the code)testwidget and observe the memory usage not increasingExpected behavior
The memory usage of the ironbar process should not increase.
System information:
Configuration
Config
Widget lua code
Additional context
I observed this behavior on two computers, both on Arch Linux.
@kafeinnet commented on GitHub (May 12, 2025):
To be sure, I graphed the memory usage with and without a cairo plugin (and my full config).
With a cairo widget:
Without a cairo widget:
@JakeStanger commented on GitHub (May 12, 2025):
Thanks for the detailed report. What's the unit for the bottom axis?
@kafeinnet commented on GitHub (May 12, 2025):
That's the time in seconds since the measuring started (one measure per second).
@JakeStanger commented on GitHub (May 14, 2025):
Got it. Turns out if you increase a reference count you gotta decrease it again. Who knew...
Not even Rust is safe.
I've made some slight changes elsewhere that should have a (very small) improvement on memory/performance in addition.