Opened 11 years ago
Closed 11 years ago
#12509 closed defect (fixed)
VirtualBox COM server bug
Reported by: | JustTryingToHelp | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
Hi. I'm trying to report a VirtualBox COM server bug which affects VBoxManage.exe and VirtualBox.exe. It appeared in VirtualBox 4.2.20.
Host OS: Windows XP SP3 x86, Windows 7 SP1 x64 VB Version: 4.3.6
How it affects VBoxManage.exe:
I close any VirtualBox.exe and VBoxSVC.exe processes. I issue a VBoxManage command (started as normal user or as an administrator, it doesn't matter, no change), I wait an amount of time between 6 sec and the moment VBoxSVC process closes and I issue another VBoxManage command. This time it doesn't do anything for 30 sec and shows this message:
VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available) VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start. Press any key to close this window...
How it affects VirtualBox.exe:
I close any VirtualBox.exe and VBoxSVC.exe processes. I start a VB VM directly. If I close it and in that time interval I start the VB Manager, it fails to start and I get the same error. Or if I start the VB Manager, close it and start a VM...
Could not attach a VBox.log file because it is not generated. But I will post a VBoxSVC.log file instead...
Attachments (4)
Change History (13)
by , 11 years ago
Attachment: | VBoxSVC.zip added |
---|
by , 11 years ago
Attachment: | batch test file.zip added |
---|
by , 11 years ago
Attachment: | screen capture video.zip added |
---|
by , 11 years ago
Attachment: | VirtualBox Manager and VM start error.zip added |
---|
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Small correction: it seems the bug appeared in 4.2.0 version. I haven't notice it in [4.2.0...4.2.18] before because it has a rather narrow time interval (about 1 sec) in which it crashes.
But if 1 sec was, let's say, almost acceptable, 6..7 sec in [4.3.0..current] is very unacceptable.
comment:4 by , 11 years ago
We are working on a fix but the fix will be too invasive and therefore it will not be part of the 4.3.8 release. Most likely this fix will be part of the next major release.
comment:6 by , 11 years ago
Actually we decided to backport the relevant fixes to VBox 4.3.x so it will be part of the next 4.3.x maintenance release. Here is a test build which includes these fixes. Any feedback is welcome.
comment:7 by , 11 years ago
Sorry for the delay but I wasn't notified about new posts (by the bugtracker). I performed some simple tests and so far I found no problems with the VirtualBox COM server. Very good job, thank you. I will try with some complex tests in the next few days.
comment:8 by , 11 years ago
All seem ok.
After releasing the 4.3.11 version this ticket can be closed.
Thank you again. Have a nice day.
comment:9 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks for the feedback! Fix is part of VBox 4.3.12.
Same error here, ran setup as admin.