virtualbox.org

Updated VirtualBox from 5.1.22 to 5.1.24 after updating to Solaris 11.3.22.3.0

After updating, a Windows 7 64 Bit Enterprise VM, configured to use 8GiB of RAM, now eats up all available RAM, causing the system to swap until all resources used and commands start failing, requiring a physical power-off, power-on.

I am attempting to tune settings to see if I can cap that memory usage somehow.

You're the 3rd report (so far) about something like that. The other two are on Windows hosts, but, I can't help the feeling that there is a connection here. Take a look at: viewtopic.php?f=6&t=83855

I can confirm the same experience as those users.
I can also confirm that the memory usage is at the setting before logging in.
I reduced the memory configuration from 8GiB to 6GiB, and via top -S, saw that the memory usage was @ 6GiB prior to logging in.
After logging in, the memory usage climbed until physical ram exhausted.
Thankfully I had another window open, as root, with the pkill VirtualBox command queued so that I didn't have to reboot.

Like others, I will be reverting to 5.1.22 until issue resolved.
If you need a tester, I can test changes / fixes during off hours.

Are you also running headless? Do you observe the same thing if you're running the VM as Normal or Detachable?

I do not run headless mode.
I start the VM via script, but running in attached GUI mode.
The laptop I run on, a Lenovo T-530, with NVIDIA drivers, 16GiB RAM, 500GB Samsung 850 Pro SSD

A VBox.log.zip would be appropriate at this point, so we can compare it with the rest of the reporters.

Could we continue this on topic 83855<1>? (Thank you Socratis.)

<1> viewtopic.php?f=6&t=83855