Potential memory leak v5.1.10 on CentOS 7

[Coralon]

Running a single Windows 10 (build 1607) guest on VirtualBox 5.1.10 on CentOS7 and the virtualbox process for the guest continuously consumes RAM, and it seems like the only way to free it is to shutdown the guest & restart virtualbox. I searched the forums and found similar references, but they were all for v3.x and v4.x.. nothing for v5.x.

The host system has 16GB RAM.
Initially, I had the Win10 guest with 12GB of RAM.. but after a few days, the vbox process was up to 16GB, and CentOS was starting to use the swap pretty heavily (and of course, performance just tanked).
I changed the Win10 guest down to 10GB of RAM, but its already back up to 14.3GB after 3 days..

Thanks,

Coralon

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[Coralon]

Thank you.. I found 4 logs, and they are in the 7zip file..

Coralon

[Perryg]

Please only send the log that shows the actual issue. Looking through a lot of logs for a single issue takes too much of anyone’s time.

I suspect that the "potential leak is not real a leak from VBox but rather the way the host is driving the application. Your issue seems to be starting due to 3D acceleration ( see below )

Code: Select all

48:01:00.432446 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :=>DxgkDdiQueryCurrentFenceNew
48:01:00.481870 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2257299), u32FenceCompleted(2257297) u32FenceProcessed(2257297)

Suggested work-a-round is to disable 3D acceleration in the guest. You can also raise a ticket at bugtracker but others that have done this the outcome was not that great.