High memory usage in xfce?
1.5.2-1 webupd8 xenial0 on xubuntu
I'm seeing that multiload-ng has this memory usage:
# htop
...
PID USER PRI NI VIRT RES SHR S CPU% MEM% DISK READ DISK WRITE TIME+ Command
19194 paolo 20 0 852M 478M 20496 S 0.0 6.0 0.00 B/s 0.00 B/s 0:00.00 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libmultiload-ng.so 19 188744
...
There are 3 multiload-ng lines in htop listing
# top
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3195 paolo 20 0 873496 490824 20760 S 0,0 6,0 9:29.32 panel-19-multil
I'm using 5 graphs: processor, ram, swap, net, disk
I have 8GB ram, 6% seems a very high usage....
Or am I missing something?
Hello, thanks for your feedback.
You are absolutely right, Multiload-ng should use about 40 MB (peak value) in most systems.
Which version of Multiload-ng are you using?
1.5.2-1
I'm sorry, I didn't notice that you already wrote Multiload-ng version.
v1.5.2 already solved several memory leaks that caused even higher RAM usage. Seems like there are a few left.
How long was Multiload-ng (or the panel that hosts it) running? Can you show me the memory usage straight after a restart?
I will fix this as soon as possible. I might ask you some other information when I better figure out the root of the problem.
Well, things are going better after a restart:
# htop
PID USER PRI NI VIRT RES SHR S CPU% MEM% DISK READ DISK WRITE TIME+ Command
3496 paolo 20 0 304M 23304 19336 S 0.0 0.3 0.00 B/s 0.00 B/s 0:00.00 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libmultiload-ng.so 19 125829
What does the 304M Virt size mean?
MEM% is growing up as with time: now, 11 hours after the restart, it's already at 1%
MEM% is 4.5% after exactly 3 days, 360MB. It had begun with 23kB. Memory grows with a pace of 5 MB/hour
Memory grows with a pace of 5 MB/hour
Thank you for extended testing! I am currently working on a huge update that will solve all those issues :)
What does the 304M Virt size mean?
This is the VSS (Virtual memory), that is the total memory available to the process (including swapped memory and shared libraries). The counterpart is RSS (Resident memory), that is the amount of physical RAM used by the process in that moment.
Little update: after further analysis, it's almost certain that those leaks are related to GTK or Cairo rather than to the program itself.
I am currently developing the next major release of Multiload-ng (2.0) that is rewritten from scratch without graphical dependencies (this dramatically reduces memory leaks and memory usage overall).