search

greshake / i3status-rust

Very resourcefriendly and feature-rich replacement for i3status, written in pure Rust
GNU General Public License v3.0
2.88k stars 475 forks source link

Possible memleak #176

Closed Drogglbecher closed 5 years ago

Drogglbecher commented 6 years ago

Hi,

since the last update there seams to be a memleak in the status bar implementation, at least I run out of memory when using it and it stops by shutting the bar down. Could you please check this? I use version 0.9.0.

Best Sebastian

lausek commented 6 years ago

Which configuration are you using?

Drogglbecher commented 6 years ago 
theme = "bad-wolf"
icons = "awesome"

[[block]]
block = "music"
player = "spotify"
buttons = ["play", "next"]
max_width = 40

[[block]]
block = "memory"
display_type = "memory"
format_mem = "{Mup}%"
format_swap = "{SUp}%"

[[block]]
block = "cpu"
interval = 1

[[block]]
block = "sound"

[[block]]
block = "xrandr"
interval = 2
icons = true
resolution = true

[[block]]
block = "time"
interval = 60
format = "%a %d/%m %R"
greshake commented 6 years ago

Very interesting! Please collect more information. I've already noticed some performance leak on my system (somehow, i3bar ramps up in CPU usage although there is no increased throughput). Maybe the two are connected?

richard-uk1 commented 6 years ago

This problem cannot come from i3status-rust. It must come from one of the dependencies. Since most of the dependencies are pretty core to the rust ecosystem it would be good to figure out what causes the memory usage.

If it happens every time, then you could start it with valgrind and debug symbols, and then once it started hogging memory, kill the process and recover the valgrind output. This might tell us where the leak is coming from.

atheriel commented 5 years ago

This was probably a dupe of #290.