Please reopen bug 662764 - by Petr Vones

Status : 


Sign in
to vote
ID 785380 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 4/23/2013 5:54:36 AM
Access Restriction Public


Please reopen bug The issue is still easily reproducible with both Visual Studio 2010 SP1 and 2012 Update 2. Suggested workaround published here does not help at all.
Sign in to post a comment.
Posted by Dave [MSFT] on 5/8/2013 at 3:59 PM
That is fantastic! Thank you for following up.
Posted by Petr Vones on 5/8/2013 at 10:25 AM
There response from VirtualBox staff is that the issue is confirmed and will be fixed in next major release 4.3 (see
Posted by Petr Vones on 4/30/2013 at 3:30 AM

I don't have any reposnse from them yet. But there are definitely more users affected by the issue. We were able to minimize the test example keeping its 100% reproducibility to a simple console application, no threading is involved.

Basically if a breakpoint is on source code line that calls a method (directly or as a property gettter/setter), the AccessViolationException or SEHException occurs in a while just by few runs through the line. If there is a simple assignment, it never occurs. Check the example and discussion here

namespace ConsoleApplication1
class Program
    static void Main(string[] args)
     for (int i = 0; i < 1000; i++)
        M1(i); // <- put breakpoint here, press and hold F5 key, AccessViolationException or SEHException occurs
     } // <- here it never occurs

    private static void M1(int i)

While I still think it is rather a VirtualBox issue (broken thread synchronization - memory corruption, cpu cache coherence ?), it is weird that any other multithreaded code (that does not run under the VS debugger) runs fine on VirtualBox. Hardware virtualization is enabled and used. It also does not happen when debugging native C++ Win32 application. Any clue why there is the problem when call stack is involved with a breakpoint only ?
Posted by Marc [MSFT] on 4/24/2013 at 6:01 PM
Thanks. Feel free to let us know if they respond.
Posted by Petr Vones on 4/24/2013 at 2:16 PM
Marc, thanks for confirmation of the issue. I already posted it to their support forum
Posted by Marc [MSFT] on 4/24/2013 at 1:22 PM
Hello Petr,

It sounds like this is an issue with Virtual Box. We are not aware of how to fix this on our side so we would recommend reaching out to Oracle with the feedback that their product breaks Visual Studio in a particular way. We don't have a good other suggestion for you.

Sorry for the inconvenience.

Marc Paine
Visual Studio Debugger QA Lead
Posted by Helen [MSFT] on 4/23/2013 at 11:42 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 4/23/2013 at 6:54 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(