Ours is a very large, mixed mode (managed/native) C++ application. Debugging with VS 2012, we've noticed some places in our managed code where, when our breakpoint in that code is hit, VS 2012 basically hangs for one minute or more. When control actually does come back to the debugger, and I step again, the 1-minute-plus hang occurs again. Looking in Task Manager, devenv.exe has one of my four cores locked up at 25%. Tried it on my co-worker's machine, same exact problem. Tried moving the function to a different .cpp file, made no difference.This is a regression because VS 2010 can step through this code with no hesitation whatsoever.Note that we have a lot of managed code in which we can set breakpoints, and VS still stop and step just fine, no hang. It's not at all clear what the difference is, but all the cases I've seen have occurred in the context of InitInstance().My co-worker had the brilliant idea of attaching another instance of Visual Studio to the Visual Studio instance that was hung, breaking, and trying to get some call stacks. Oddly, on his machine, the process that was locked up was msvsmon.exe, as though he was remote debugging, which he was not. For me, the process is devenv.exe. We grabbed one call stack from his machine and I grabbed several from my machine (let it run for awhile, break, get a call stack, go for a while, break and get another call stack, etc.). I will attach those after submitting this. I will also attach the C++ code for the function where stepping is performing so badly in case it helps.We do have update 1 of VS 2012.
Visual Studio/Team Foundation Server/.NET Framework Tooling Version
Steps to reproduce
Operating System Language