Opened 3 years ago
VirtualBox crashes with hardened memory allocator Hardened Malloc on the host
|Reported by:||adrelanos||Owned by:|
|Guest type:||all||Host type:||Linux|
When using hardened memory allocator Hardened Malloc on the host operating system Debian
buster VBoxSVC crashes after arround 30 minutes even during inactivity.
A critical error has occurred while running the virtual machine and the machine execution should be stopped. For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log, which you can find in the virtual machine log directory, as well as a description of what you were doing when this error happened. Note that you can also access the above file by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK to power off the machine.
VirtualBox VM log:
all OK no more log entries for 30 minutes while VM is working OK then the only new log additions are these: 00:18:45.237389 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED) 00:19:16.904964 VirtualBoxClient: detected working VBoxSVC (rc=NS_OK)
tail -f ~/.config/VirtualBox/VBoxSVC.log
all OK no more log entries for 30 minutes while VM is working OK no new log entry after crash The log ends there after crash then becomes ~/.config/VirtualBox/VBoxSVC.log.1
Will a VirtualBox core dump be required? Or something else? Is this a bug you would be interested in fixing or out of scope?
Hardened Malloc installed inside the VM is functional. Hardened Malloc on the host crashes VirtualBox after a while.
Could you please make VirtualBox compatible with Hardened Malloc?
VirtualBox compatibility with Hardened Malloc might be usable to reveal some memory corruption bugs inside VirtualBox.