Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
Opened by Muflone (muflone) - Tuesday, 09 August 2022, 11:51 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 09 August 2022, 20:49 GMT
|
DetailsDescription:
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
Tuesday, 09 August 2022, 20:49 GMT
Reason for closing: Upstream
Additional comments about closing: upstream issue, see comments for a fix
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?
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
I've created a new user and ran virtualbox from there without any issue, so there's something in my virtualbox profile affecting
HOME=$PWD/test-virtualbox LANG=C virtualbox
run without any issue, creating a new virtualbox profile
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
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
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!