Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Apr 2019 19:21:11 +0000
From:      bugzilla-noreply@freebsd.org
To:        vbox@FreeBSD.org
Subject:   [Bug 236616] emulators/virtualbox-ose: Unable to create a new machine due to "Unexpected exception: cxxrt::bad_alloc [St9bad_alloc]"
Message-ID:  <bug-236616-26505-6wI3fdG6wN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-236616-26505@https.bugs.freebsd.org/bugzilla/>
References:  <bug-236616-26505@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236616

--- Comment #7 from Dimitry Andric <dim@FreeBSD.org> ---
(In reply to Mateusz Piotrowski from comment #2)
> Here are some additional error messages I get when running "vagrant up" to
> create a new machine:
> 
> > There was an error while executing `VBoxManage`, a CLI used by Vagrant
> > for controlling VirtualBox. The command and stderr is shown below.
> > 
> > Command: ["import", "-n", "/home/0mp/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-bionic64/20190219.0.0/virtualbox/box.ovf"]
> > 
> > Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> > Interpreting /home/0mp/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-bionic64/20190219.0.0/virtualbox/box.ovf...
> > OK.
> > VBoxManage: error: Output argument aExtraConfigValues points to invalid memory location (0000000000000000)
> > VBoxManage: error: Details: code NS_ERROR_INVALID_POINTER (0x80004003), component VirtualSystemDescriptionWrap, interface IVirtualSystemDescription, callee nsISupports
> > VBoxManage: error: Context: "GetDescription(ComSafeArrayAsOutParam(retTypes), ComSafeArrayAsOutParam(aRefs), ComSafeArrayAsOutParam(aOvfValues), ComSafeArrayAsOutParam(aVBoxValues), ComSafeArrayAsOutParam(aExtraConfigValues))" at line 387 of file VBoxManageAppliance.cpp
> 
> Tested on FreeBSD 13.0-CURRENT r345294 GENERIC amd64, vagrant-2.2.4_1,
> virtualbox-ose-5.2.26_3.

I can reproduce these, but I have no clue what causes it. The code is hard to
follow due to all the macros and object interfacing... It doesn't throw here,
at least, so I don't see any bad_alloc exceptions.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236616-26505-6wI3fdG6wN>