2

I'm getting a message box pop up with the following message half way through a debugging session. This is happening intermittently but every time it blows, I have to restart VS2012 and IIS express which is pretty annoying and is losing 10 minutes every time it goes bang.

A fatal error has occurred and debugging needs ot be terminated. For more details, please see the Microsoft Help and Support web site. HRESULT=0x80070000e. ErrorCode=0x0.

This points to out of memory but I've got 24GiB of RAM in this box and am running Windows 7 x64 Pro. ProcMon is reporting 37% RAM used. I've got a 320GiB SAS disk with 110GiB free as well so it's not disk space!

Does anyone know what this is?

There is a connect case open but as usual, it's damn useless as nothing has been done.

pointyhat
  • 167
  • 1
  • 1
  • 10
  • 24 GB of RAM doesn't do you any good for 32-bit processes. Keep an eye on the commit size for devenv.exe in Task Manager as well as the kernel memory pool usage. Disable add-ins. – Hans Passant Sep 19 '13 at 16:36
  • 1
    Thanks - I have no add-ins loaded. VS is hitting over 3Gb RAM which might be the problem. VS is a useless piece of junk. – pointyhat Sep 20 '13 at 08:41
  • @pointyhat Have you managed to overcome this? What have you done? I'm experiencing this in VS2012 Update 4. – MilkyWayJoe May 14 '14 at 19:00

2 Answers2

0

Could it be an extension conflict, similar to this answer indicating that an expired trial of Redgate Reflector was throwing a NullReferenceError?

Have you considered that it could be recursive code resulting in a stack overflow? Similar to what this answer reported or this one. The real question is, of course, how do you identify the recursion without stepping through everything...

Community
  • 1
  • 1
drzaus
  • 24,171
  • 16
  • 142
  • 201
0

I found toggling the "Set as Startup Project" option found by right clicking a project in the Solution Explorer, to another project, starting a debugging session and then you can switch back to the original start up project and every thing works again.

I had this happen to be debugging a test, so in that context, the start up project is not even important but that did not matter, I was getting this error message all the same.

Brian Ogden
  • 18,439
  • 10
  • 97
  • 176