Hi all,

Since some days ago I have problems to debug a web application with aspx and VB code with Visual Studio .NET. Every time I step to the next instruction with the debugger the PC gets hung for about ten seconds and the CPU usage goes almost to 100% for process devenv.exe. It happens with all instructions, no matter their complexity (even a simple step from 'else' to the next instruction).
I have not made any significant change as far as I know, everything was running OK and suddenly the debugging became so slow that is almost impossible. The execution and other Visual Studio operations are normal, I only have problems when stepping through the code.

Software environment:
MS .NET framework 1.1 Version 1.1.4322
MS Dev. Environment 2003 Version 7.1.3088
Microsoft Visual Basic .NET 69535-270-0000007-18929
Language: spanish
IIS 5.1
Internet Explorer 6.0 with SP1
OS: Windows XP professional SP1, language: spanish
I have installed all pending critical updates with Microsoft Update.

I heard that a service pack for .NET framework 1.1 is about to be released. Is my problem already detected and fixed in the SP, or in any fix? When will it be available?

Thanks and regards.

Hi Diana. Were you able to solve your problem ?

I have this same problem on a new box I just built with VS.NET 2003.

Hi,

Today I seem to have solved the problem. I have a permanent breakpoint in one of my lines of code. By chance I went to the window 'Breakpoints' and found that I had several hundreds of entries under that breakpoint, each one reporting that the breakpoint had been visited. I deleted all of them (but not the breakpoint itself). After that my VS goes smooth again, no delay or CPU 100% use on debugging.
It seems to me that this is not a desirable feature of Visual Studio, as I didn't change any default breakpoint configuration value, so it could happen to anyone without any explanation.
I hope this post will help other people.

Best regards,

Diana

Diana,

I was experiencing the same behavior that you described above and found the same situation within my Breakpoints window. After purging the breakpoints the problem corrected itself. Thanks for posting your solution. You saved me some time and trouble. I agree that this is indeed an undesirable "feature" within the IDE.

Tony

Had the same problem. Debugging a webapplication suddenly decame dead slow. It took more than 1 minute to let IE debug session pop-up.

After reading this post I tried to open my break-points window... and it was extreme slow as well. Had to ctrl+alt+del and end my Visual Studio process.

After manually clearing out some 20 break points from my code. I tried my breakpoint window again ... and yes after a minute I got the list with an other 30 breakpoints or so.

After clearing all those, my debugging sessions became smooth and painless again.


--W

Had the same problem. In my case I couldn't type/edit code in the editor, But I was able to debug and run fine.

Thank you guys for this post. It saved me lot of time.

Thanks,

Thanks for posting the solution to this problem, I've tried many things, renaming some DLLs (debugging symbols DLLs), disconnecting the project from the source code control (CVS), removed some DLLs and nothing worked until this.

I noticed there were not so many breakpoints, about 30, but it already became my debugging tasks a nightmare.

Thanks again!

solution helped thanks so much Diana

Chau 

Diana, Thanks very much for posting the solution. Prabu G

I have not found the posted resolutions to solve the problem. 

 

I have this same problem in Visual Studios 2005 while writting SSRS reports. I don't use breakpoints while writting reports and the problem still occurs %75 of the time for no apparent reason. I am running .net framework version 2.0

 

Thank's a lot. It really helped me out!

Failing to plan is Planning to fail