Devenv.exe Hangs on Run

[Selden McCabe]

Has anybody experienced this problem?
I have a solution that consists of 6 or 7 projects.
Every so often (2 or 3 times a week) when I click Run, everything builds
seemingly OK, but then, just when I would expect the app to start, nothing
happens, and the task manager shows devenv.exe sitting at 100% cpu, fixed
memory (about 127 Megs), forever. The only way out is to kill it from the
task list.

When this happens, I can usually fix it by deleting the OBJ folder under the
main project. But once in a while, this doesn't work. In those cases, I've
tried deleting ALL the OBJ and BIN folders under all the projects, and
sometimes it still happens.

So far, when I'm totally stuck like that, I delete the entire source tree
and get it again from Source Safe.

What is going on? How can I prevent this?

Thanks,
---Selden

[Nick Malik]

Have you seen this:
http://blogs.msdn.com/andypennell/ar.../13/72617.aspx

Also this:
http://support.microsoft.com/default...;EN-US;Q326098

Note: if you have Framework 1.1 SP1, the bug described in the KB article
above is fixed.
http://msdn.microsoft.com/netframewo...sptechpreview/

Hope this helps,
--- Nick

"Eric Beaudry" <eb**********@nospam.nospam> wrote in message
news:A4**********************************@microsof t.com...

We do experiment that kind of problem too. We have a solution with 43
projects so you can imagine how often it can happen here!

We've been able to see that the memory usage of devenv.exe is continualy
rising(on each run with debugging) and when we approche 300 megs we start
having strange results. One of these is "debugger can't attach to process and hang" until we hit the stop button.

Are you having the same evidences?

Eric Beaudry
"Selden McCabe" wrote:

Has anybody experienced this problem?
I have a solution that consists of 6 or 7 projects.
Every so often (2 or 3 times a week) when I click Run, everything builds
seemingly OK, but then, just when I would expect the app to start, nothing happens, and the task manager shows devenv.exe sitting at 100% cpu, fixed memory (about 127 Megs), forever. The only way out is to kill it from the task list.

When this happens, I can usually fix it by deleting the OBJ folder under the main project. But once in a while, this doesn't work. In those cases, I've tried deleting ALL the OBJ and BIN folders under all the projects, and
sometimes it still happens.

So far, when I'm totally stuck like that, I delete the entire source tree and get it again from Source Safe.

What is going on? How can I prevent this?

Thanks,
---Selden

[Eric Beaudry]

Those are really about the fact that the debugger hangs, which is fine since
the title of the post is exactly that! So I'll try your suggestions.

Do you have any ideas about the memory consuption problem. Everytime we
start the solution we end up with more memory allocated to devenv.exe.
Sometimes up to 700 megs! This is probably part of the problem too, since the
debugger rarelly survive the next run!

We have noted that if we stop the debugger "with the stop button" instead of
closing the browser (we are debugging an ASP.net solution) we regain a bit
more of that allocated memory.

Any ideas are welcome,
Thanks


"Nick Malik" wrote:

Have you seen this:
http://blogs.msdn.com/andypennell/ar.../13/72617.aspx

Also this:
http://support.microsoft.com/default...;EN-US;Q326098

Note: if you have Framework 1.1 SP1, the bug described in the KB article
above is fixed.
http://msdn.microsoft.com/netframewo...sptechpreview/

Hope this helps,
--- Nick

"Eric Beaudry" <eb**********@nospam.nospam> wrote in message
news:A4**********************************@microsof t.com...

We do experiment that kind of problem too. We have a solution with 43
projects so you can imagine how often it can happen here!

We've been able to see that the memory usage of devenv.exe is continualy
rising(on each run with debugging) and when we approche 300 megs we start
having strange results. One of these is "debugger can't attach to process

and

hang" until we hit the stop button.

Are you having the same evidences?

Eric Beaudry
"Selden McCabe" wrote:

Has anybody experienced this problem?
I have a solution that consists of 6 or 7 projects.
Every so often (2 or 3 times a week) when I click Run, everything builds
seemingly OK, but then, just when I would expect the app to start, nothing happens, and the task manager shows devenv.exe sitting at 100% cpu, fixed memory (about 127 Megs), forever. The only way out is to kill it from the task list.

When this happens, I can usually fix it by deleting the OBJ folder under the main project. But once in a while, this doesn't work. In those cases, I've tried deleting ALL the OBJ and BIN folders under all the projects, and
sometimes it still happens.

So far, when I'm totally stuck like that, I delete the entire source tree and get it again from Source Safe.

What is going on? How can I prevent this?

Thanks,
---Selden

[Selden McCabe]

Although I don't understand why it works, I have found a work-around:
In my case, I created a NEW solution, and then added the existing
projects one-by-one back into the solution.

Now it loads, compiles, and runs normally.

If you haven't tried this, see if it works for you (although 64 projects
is a lot of work!)

---Selden

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!