| 1 | | Microsoft Visual Studio Debugger QA staff resolution https://connect.microsoft.com/VisualStudio/feedback/details/785380/please-reopen-bug-662764 is ''"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."'' |
| | 1 | Microsoft Visual Studio Debugger QA staff resolution https://connect.microsoft.com/VisualStudio/feedback/details/785380/please-reopen-bug-662764 is '''''"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."''''' |
| | 2 | |
| | 3 | There is '''100% reproducible test case''' attached. Detailed steps to reproduce it: |
| | 4 | |
| | 5 | 1. download attached MemoryLeakTest.rar |
| | 6 | 2. extract (better to delete 'bin' and 'obj' directories) and open the solution in Visual Studio 2012 or 2010 |
| | 7 | 3. open NumberCounter.cs in code editor |
| | 8 | 4. goto line 79, put breakpoint there |
| | 9 | 5. press F5 (Run) |
| | 10 | 6. press 'Start' button on the form |
| | 11 | 7. when the debugger stops at the breakpoint, press and hold F10 key |
| | 12 | |
| | 13 | The debugged application will crash with AccessViolationException after approx 10 seconds. If you enable "Native code debugging" in the example project it will take more time to crash and the AV address is still the same, see the ticket comments for details. Note that it never happens in non-virtualized environment or using VMware. |
| | 14 | |
| | 15 | System information: Visual Studio 2012 Update 2 or 2010 SP1, VirtualBox 4.2.12, Core i5 2540M, VT-x enabled, Nested Paging disabled, 2 virtual CPU configured, Windows 7 x64 host, Windows Server 2008 R2 x64 guest. |
