Closed mersinvald closed 9 years ago
If needed, I can also make gcore dump file
The problem (as I see it) is i3bar parsing the whole JSON every second, and, as it's grow, this process takes more and more time and memory.
I'm fairly confident that it doesn't (this would affect almost every user, which it doesn't). What makes you think that?
Anyway, I don't see that this would be related to i3-gaps. Please reproduce this with vanilla i3 and report it at i3/i3. If you cannot reproduce it with vanilla i3, drop a comment here and we will reopen it.
In preparation for the ticket at i3, please provide an i3bar log file (see the debugging docs in the current "next" branch) and also disable i3bar and just run the conky command in a terminal for a while to see if this produces a mem leak.
I'm using conky with JSON output as statusline provider for i3bar. The problem (as I see it) is i3bar parsing the whole JSON every second, and, as it's grow, this process takes more and more time and memory. This leads to hard memory leak and really huge slow down after ~20 minutes.
Here are my measurements. i3 resources consumption after:
Launch RAM: <1% (~20MB) CPU:1%
5 minutes RAM: ~3% (~115MB) CPU: ~3.3%
Delays becomes as big so I can feel `em: RAM: ~20% (~800MB) CPU: ~30%
i3bar:
i3bar-conky.sh
conkyrc
i3 --version
conky --version
umane -a