Home Dashboard Directory Help
Search

VS 2013 startup hang with VirtualBox if D3D drivers installed but 3D acceleration is not enabled by robertknight2


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 800921
Opened: 9/16/2013 3:33:48 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Visual Studio 2013 RC hangs during startup when run in a VirtualBox guest with the following setup:

1. Windows 7 guest running under VirtualBox 4.2.18
2. VBox Direct3D drivers installed
3. 3D acceleration *disabled* under VBox settings for the guest (this is the default setting)

Stack traces captured from a dump using VS 2010:

>    ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes    
    ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes    
    wpfgfx_v0400.dll!71b21715()     
    [Frames below may be incorrect and/or missing, no symbols loaded for wpfgfx_v0400.dll]    
    wpfgfx_v0400.dll!71b212c6()     
    wpfgfx_v0400.dll!71b4b75a()     
    kernel32.dll!@BaseThreadInitThunk@12() + 0x12 bytes    
    ntdll.dll!___RtlUserThreadStart@8() + 0x27 bytes    
    ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes    

>    ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes    
    ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes    
    VBoxDispD3D-x86.dll!6123713f()     
    [Frames below may be incorrect and/or missing, no symbols loaded for VBoxDispD3D-x86.dll]    
    VBoxDispD3D-x86.dll!61236839()     

After changing the settings to enable 3D acceleration for the guest VM, the problem does not occur.
Details
Sign in to post a comment.
Posted by Microsoft on 5/13/2014 at 12:54 AM
Thanks for your quick response. Based on current status, this bug is not actionable if we do not have any useful information. I would like to ask your permission to close this feedback. Should you find any bugs in the future, please feel free to let us know.
Posted by robertknight2 on 5/12/2014 at 6:36 AM
I'm not able to reproduce the issue with the combination of:

- Windows 8.1
- VirtualBox 3.4.10 on host running OS X 10.9.2
- Visual Studio 2013 - 12.03 Update 1
Posted by Microsoft on 5/12/2014 at 3:21 AM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.

Based on current status, this bug is not actionable if we do not have any useful information. If we haven't heard back from you with the requested information in the next days, we will go ahead and close the issue.
Posted by Microsoft on 5/8/2014 at 7:55 PM
Hi robertknight2,

Thanks for your feedbback. Unfortunately. we couldn't repro the issue internally according to your descriptions. In order to efficiently investigate this issue, we need here is a minidump file at the point of the hang. Could you please refer to the following steps to collect a dump file?

Visual Studio now has an extension called Microsoft Visual Studio 2013 Feedback Tool, available on the VS gallery(<http://visualstudiogallery.msdn.microsoft.com/563d1003-f0ed-498f-8ef9-f8ee1aac39fe>)

1. Start Microsoft Visual Studio Feedback Tool
2. Select "Add to an existing feedback"
3. Select type: Hang
4. Record a repro: When the dialog box appears, select the running Visual Studio instance that hanged. VSFT collects a dump file regarding the crash, called MiniDump.zip, and attaches to your bug report.
5. Submit

For more detail, please refer to https://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=26698

Please submit this information to us within 3 business days. We look forward to hearing from you with this information. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.
Posted by robertknight2 on 3/3/2014 at 9:14 AM
I am still able to reproduce this issue with VS 2013 final and VirtualBox 4.3.8. I have yet to test with VS 2013 Update 1.
Posted by Microsoft on 9/24/2013 at 3:42 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 9/19/2013 at 11:27 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested.
Posted by Microsoft on 9/17/2013 at 7:02 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a dump file and call stack so that we can conduct further research?

We look forward to hearing from you with this information.
Posted by Microsoft on 9/17/2013 at 5:49 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 9/16/2013 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by robertknight2 on 9/16/2013 at 3:35 AM
1. Enable 3D acceleration under guest settings for the VirtualBox VM (Tested)
2. Unininstall D3D drivers for VirtualBox VM (Not tested)