pve-manager has a memory leak

mir

Famous Member
Apr 14, 2012
3,568
127
133
Copenhagen, Denmark
Memory usage before login: 91.1 MB
Memory usage at start: 120.4 MB
After 5 min. without doing anything: 300.2 MB
After 10 min. without doing anything: 451.1 MB
after 25 min. without doing anything: 803.2 MB
And still counting.

Status: sleeping
% CPU: 4-10%

If you never login the memory usage stays at 91.1 MB so my conclusion is that something starts after you login that leaks memory in the browser.

Google Chrome: Version 24.0.1312.57
OS: Debian GNU/Linux SID AMD86_64


pveversion -v
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-72
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1
 
I do not see this here.

dig deeper on your box, which processes? do you see this on all your Proxmox VE installations?
 
It is not a process on the server it is the process running in your browser. Eg. the web-gui is leaking memory and by the nature of the code it must be in the java-script part, maybe even extjs. The behavior is a result of the latest upgrade. My test did not include having a console open so we can exclude the Java plugin in the browser. Since this is tested in google chrome, and because google chrome opens a new process per. tab you can be very certain that the process running in each tab uses memory without intervention from other open tabs at the same time.
 
Firefox (iceweasel 10.0.12)

start: 151.4 MB
After login: 154.4 MB
After 5 min: 167.1 MB
after 15 min: 167.3 MB

It seems google chrome is the guilty part!!!
 
ah ok, I will monitor it here. my primary desktop is win7-64 - so far I cannot see the issue - so what desktop OS do you run in detail? I will try to reproduce.
 
I can confirm this on Windows 8 Pro 64bit
Google Chrome 24.0.1312.57
It's a little misleading in the new Windows 8 task manager. The process for the proxmox tab does not show a problem. It sayed around 53mb the whole time. I only had the 1 tab open.
If you scroll down into the background processes, you see 3 more google chrome processes.
The 2nd and 3rd stay around the same.
The 1st background google chrome process is growing.


Start 32.8MB
after login 62.23MB
5 minutes 150MB
15 minutes 354MB
20 minutes 430MB
 
It is not a process on the server it is the process running in your browser. Eg. the web-gui is leaking memory and by the nature of the code it must be in the java-script part, maybe even extjs. The behavior is a result of the latest upgrade. My test did not include having a console open so we can exclude the Java plugin in the browser. Since this is tested in google chrome, and because google chrome opens a new process per. tab you can be very certain that the process running in each tab uses memory without intervention from other open tabs at the same time.
Hi,
it's don't happens with chromium on sid (Version 22.0.1229.94 Debian wheezy/sid (161065)).

Udo
 
I also see the issue with Chrome 24. Now I test with 26.0.1403.0 canary, so far it looks good, no memory growing.
 
Google-chrome-beta (25) epic fail.
Google-chrome-unstable (26) Seems to work.
iceweasel 10.0.12 Seems to work.
Chromium (22) to a lessor extend epic fail. But memory consumption still rises.
Opera (12.14) Seems to work.

I begin to suspect that either pve web-gui or extjs is causing the memory leak as it seems that the memory consumption grows after every automatic gui update.

I am going out now but will let all browser stay open

Memory consumption now:
Google-chrome-unstable 153.8
iceweasel 10.0.12 267.7
Chromium (22) 188.8
Opera (12.14) 152.1
 
4 hours later:
Google-chrome-unstable 163.5
iceweasel 10.0.12 270.5
Chromium (22) 207.2
Opera (12.14) 200.4

Conclusion: google-chrome > 22 and < 26 is leaking memory to such an extend that it should be avoided at all cost.
 
I noticed this issue as well in win 7 64bit running chrome 25. Thanks for figuring it out.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!