Opened 8 years ago
Closed 8 years ago
#15726 closed defect (fixed)
VirtualBox Manager crash on exit
| Reported by: | Mihai Hanor | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
Hello,
I can reproduce a crash of the VirtualBox Manager, under my Windows 10 64 bit host. It seems it crashes when I close the Manager window, after I've started a VM using the Manager. I'm sending Frank an e-mail with a Google Drive link to a full memory crash dump of VirtualBox-5.1.3-109189-Win. I can also reproduce it with the 5.1.2 release, the crash looks identical.
Attachments (1)
Change History (8)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Unfortunately we are not able to reproduce. Maybe some different host configuration ...
comment:3 by , 8 years ago
Open the VirtualBox Manager, create and start an empty VM (no boot medium), wait for it to show you the "Fatal: no bootable medium found!" message and close the Manager. You can open the Manager again, for another attempt, without disturbing the VM. For me, it crashes almost every time.
comment:4 by , 8 years ago
I've attached a windbg log, showing the access after unloading of VBoxProxyStub.
comment:5 by , 8 years ago
Mihai, we think we fixed the crash -- the fix is actually more a hack but it should work for now. Could you test the latest test build from here? Your reproduction scenario was very helpful, thanks!
Just wanted to let you know that we downloaded and analyzed the dump you provided us, thank you! It looks like VBoxProxyStub is unloaded too early. At the moment we don't know why.