FS#75563 - [virtualbox] high memory usage during the startup with no started VM

Attached to Project: Community Packages
Opened by Muflone (muflone) - Tuesday, 09 August 2022, 11:51 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 09 August 2022, 20:49 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Since upgrading virtualbox to 6.1.36, regardless the kernel used, starting virtualbox the whole free memory is filled until the system hangs. Killing the VBoxSVC process the system restores but Virtualbox closes.

Downgrading the virtualbox+virtualbox-host-modules to 6.1.34-4 virtualbox works again

Additional info:
* virtualbox 6.1.36-1
* linux versions: 5.18.16.arch1-1, 5.19.arch1-1, lts 5.15.59-2
* unsure if it's related to https://www.virtualbox.org/ticket/21036 as I've no running VM at all

Steps to reproduce:

- reboot the system
- start virtualbox
- observe via htop the memory usage which starts to increase until the system hangs (tested up to 16 GiB)
- killing VBoxSVC the system recovers
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 09 August 2022, 20:49 GMT
Reason for closing:  Upstream
Additional comments about closing:  upstream issue, see comments for a fix
Comment by Christian Hesse (eworm) - Tuesday, 09 August 2022, 12:21 GMT
How long does it take to fill up the memory? I have not seen this yet.
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 13:21 GMT
a couple of seconds, in less than 1 minute I've 16 GiB used by VBoxSVC
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 13:26 GMT
the memory usage increases of ~500 MB/s
Comment by Christian Hesse (eworm) - Tuesday, 09 August 2022, 13:37 GMT
Not for me...

Possibly this is a gui framework / theming issue? Can you select another theme and try again? And does it happen if you minimize the window?
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 13:52 GMT
The GUI is not shown at all, until I kill the VBoxSVC process

After killing VBoxSVC a virtualbox dialog appears with the error:

Callee RC: NS_ERROR_ABORT (0x80004004)

Closing the dialog, the virtualbox process closes

At 00:45 the system hung, I awaited too much, so I closed it using SYSRQ+F
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 13:56 GMT
Changing the theme from Adwaita to Arc-Darker-Polo didn't changed the issue

I've created a new user and ran virtualbox from there without any issue, so there's something in my virtualbox profile affecting
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 14:03 GMT
Attaching new video as the previous leaked personal information
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 14:07 GMT
again

HOME=$PWD/test-virtualbox LANG=C virtualbox

run without any issue, creating a new virtualbox profile
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 14:17 GMT
the issue seems related to 4 VMs out of 42

three of them are Mac OS X, one is Debian Jessie 64 bit. Removing them from the configuration file VirtualBox.xml, the application starts properly
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 15:16 GMT
I think to have found the issue:

all the affected VMs have in their configuration .vbox file the following specification which makes Virtualbox hang and eat all the available memory:

<VideoCapture enabled="false" screens="18446744073709551615" horzRes="1024" vertRes="768" rate="512" fps="25"/>

changing the screens="18446744073709551615" to screens="1" everything works properly, for all the affected VMs

Upstream bugs:

https://www.virtualbox.org/ticket/21034
https://www.virtualbox.org/ticket/21032
https://www.virtualbox.org/ticket/21030
Comment by Christian Hesse (eworm) - Tuesday, 09 August 2022, 20:09 GMT
Well, 18446744073709551615 is a lot of screens. :)

As this is known upstream and promised to be fixed in next release... Are you ok to close the issue?

If anybody can provide a link to a patch fixing this - let me know!
Comment by Muflone (muflone) - Tuesday, 09 August 2022, 20:18 GMT
I think this task can be closed as there are not patches to backport AFAIK

Loading...