FYI memory leak ipbx 13-12 ubuntu 14.04 virtualbox 5.0.0

[chris_c_]

After running for 2 days 18 hours, memory usage of ipbx 13-12 virtualbox vm "private bytes" has crept up to 1.584 GB.

Inside the vm, reports 753mb out of 1024mb used. 0mb of swap used.

The leak continues until about 2gb then the vm starts malfunctioning, becomes unusable, unresponsive, and must be shut down and started manually.

Anyone else seeing this??

 

[wardmundy]

If it doesn't crash, it's not a bug. Linux ALWAYS continues to use more and more RAM for caching. It's a "feature" not a "bug."

 

[chris_c_]

Yes but inside the VM, it is showing 900mb out of 1gb consumed, that is OK.
Outside the VM, the host operating system is showing vbox is consuming 2GB for the vm.
Host operating system is sluggish, the entire virtualbox system and all running vm's must be fully shutdown and restarted.
Is anyone else noticing this with virtualbox?
Certainly should not leave it like this - not quite "production ready" - requiring a full vbox restart every 2 days!?

 

[wardmundy]

What is the host platform? How much RAM is in the host machine? How much RAM did you assign the the VirtualBox image? What other apps are running on the host machine? All of those things will affect performance of the virtual machine. It sounds like you have insufficient RAM and CPU processing power to handle the VirtualBox-based app.

 

[chris_c_]

Host is windows 7 x64, 4gb ram.
Guest os: 1gb is assigned to the virtualbox ipbx ubunutu 14.04 vm.
CPU usage is fine, host shows 16%. WIth 12% consumed by Virtualbox ipbx ubunutu 14 vm.
The vm's memory usage, on the host side, creeps upward, beyond the 1gb assigned barrier, to 2gb, and keeps slowly rising.
From within the vm it shows 900mb used, 0 swap used, and it is staying under 1gb.
This must be a defect / memory leak in virtualbox 5 MM/GC code.

 

[wardmundy]

Maybe it's time...

 

[chris_c_]

Like the Mac OS X and it's unix-ness.
I've upgraded from virtualbox 5.0.0 to 5.0.2 see if this fixes the leak.
I don't believe it to be an issue with the windows 7 64 bit host operating system.
Previous versions of virtualbox on the same win 7 x64 ran for much longer times - weeks - without memory leaks.
Virtualbox 5.0.0 seems to have been leaking guest memory out into the host, after only 2 days.

 

[Dave Gray]

Ummm, Virtualbox 5.0.0 ? I would never use anyone's .0.0 product for anything but the most ephemeral testing - and certainly not anything from Oracle.
All joking aside, it really does take a while for software to get thoroughly wrung out. Have you been checking the Virtualbox forums to see who else is having issues? I have no problem believing they've got memory management issues. Comes with the territory...

 

[chris_c_]

5.0.2 is looking better so far. uptime 23 hours. 900mb used inside the vm. 600mb private bytes on the host side.
If it makes 7 days stable at under 1gb host ram then that memory leak problem will be solved.