Has anyone else experiance really slow debugging in VB.Net Beta 2 Yesterday was the first time I used it to step through code line by line and I was shocked. It's a simple project with one form using a datagridview and it was horrible. We are talking a 3 - 5 second delay every time I hit the F10 key to step over...
Thanks,
Aaron
Debugger is extremely slow
Hot Topic
- What is the difference between <Me> and <MyBase>?
- reading text from a document and displaying it
- Using sender as a case in Select Case Statement
- Turning Off Quick Console in VB.NET 2005 Express
- Combobox fill ip adresses
- Calling a click event
- Mirosoft Agents in VB
- isnull function
- Creating arrays of controls in VB 2005. Help!
- printing datagridview
Visual Basic
- HTML Editor in Visual Basic - HELP
- One or more errors encountered while loading the designer
- Calling SQL Server Stored Procedures in VB 2005
- Deployment of project problem, downward support from XP to 2K
- Streaming text from a view to a file.
- System.Data.OracleClient.OracleConnection?
- VB in access
- strings and arrays?
- Visual Basic Performance for 3 Million record/rows
- how to change struct to array under wince？（I have code but only run under other window platform)
Debugger is extremely slow
Hitesh811
Could someone send me a very simple project that repros this problem
I work on the VB QA Debugger team and have not noticed this problem (though there was 1 build where the performance of the debugger did go down, I do not believe this build was released externally though)
thanks in advance
Kathy @ Microsoft
VB Debugger Tester
UmeshBhavsar
betona
Now I have to do it everyday or two.
JosBoy
With the responses above, and then this one, it kind of scares me. :) I am hoping the reason that you don't experiance it is because it's fixed in the build that you are using and we are using an older one. Every single project I have ever worked on, from a small test app with a DataGridView, one dataset, and the related bindingsource, etc, it has been slow. I hit F10 to step over and I get a 3 second delay then it goes to the next line. Sometimes, that delay can take up to 5 seconds. That may not seem like much to a lot of people, but when we are trying to fix problems and have a lot of code to step through, that is not going to work for us. Especially when using VS.Net 2003 and there is no delay.
On the other side of this coin, could it be our machines I noticed the other day my IDE was dirt slow. I opened up my task manager and saw my resources completely tapped out. I have 512MB of physical ram and it was all used, and then another 1Gig of virtual ram was being allocated. This happens often. Do I now need to upgrade to 1Gig of ram If I only close the IDE, my virtual ram goes WAY down and my physical ram usage goes down to around 400Mb. Doing the math on that, it's a whole lot of ram usage.....
Daniel Joubert
Ruben Figueroa
I'm experiencing the same thing. I'm using the June CTP, and it seems worse now than before. It's too the point I'm ready to dump VS and go to Delphi. I'm spending valuable time waiting for the IDE to "recover" everytime I debug. It's intolerable. I've been watching the Task Manager when the IDE is open and there is no project or no activity at all. The CPU is still jumping around between 1 & 2 %. When I try to close the Start page, it spikes up to 50%. That just seems wrong. When I have projects open and debugging, the memory usage climbs and climbs and doesn't go back down after I've ended the debugging. Sometimes it takes more than a minute for the screen to finally refresh so I can start coding again. And try moving a window! The latency is ridiculous. I'll drag the properties window to a new location and in 20 or 30 seconds it might end up in the general vicinity of where I wanted it. This just can't be normal. There has to be some explanation and some solution.
Md Shahid Ibrahim
This has been reported to our devs via customers and sounds very similar to what everyone reported on this thread regarding the slow IDE performance (and profile resetting, perf degradation over time)
The bug has been fixed in a June build of VS so it sounds like your builds will still exhibit this behavior (much apologies)
Please don't move over to Delphi! VS 2005 Rocks!
thanks!
Kathy @ Microsoft
VB Debugger Tester
yai
Seriously though, that sounds excellent. I can't wait until we can see some of these fixes.. Do you know if they plan on releasing an update to Beta 2 so we can test out these fixes
DevilDog74
As I said, I have a team of 8 developers working with the June CTP of Visual Studio Team System (I have June CTP of Team Foundation Server running too).
Everybody is having this problem. If you have more resourcers you will have to wait a little bit more time to se the slow down, but everybody have it.
We are building a Web Site project, no big deal 10 aspx files, 10 users controls some .vb files. I don’t think this is about the files. This is about how you use de enviroment, how ofthen you move tabs around or use the debugger.
The IDE is slowing down, not just the debbuger.
The only thing the speed things up was a Reset in the Enviroment Settings.
ivolved_Mike_Brown
Yes, I'm fighting with a very slow debugger, yesterday I went to add remove programs and 'repaired' the whole installation, I got a much heathier system as a result, althought it seems as the debugger breaks into the code I get a few seconds of 100% CPU. Before the repair, creating a brand new empty vb console project created a program that just didn't run. (The background compiler complained before I even touched the run button). After the repair, creating the same project worked fine. It feels like the installation gets progressively bogged down with something that the repair resets or cleans out. I also stopped using VSHOST, but I get the feeling it didn't make a difference.... In general the IDE shoots up to 100% cpu as I change or write code. Hoping a July CTP is better, it certainly is almost unusable and I'm on amd64 3.2GHZ with raid drives and 3GB ram. (the devenv.exe *32 memory usage goes up and up and up, but perhaps theres no pressure to release the ram just yet).
Anff
Alex Marrow
Would this be sufficient for your team to try out (or have 1 of them maybe try this out to see if it solves the problem)
http://lab.msdn.microsoft.com/ProductFeedback/ViewWorkaround.aspx FeedbackID=FDBK31126#1
The other workaround is to reset your settings (which someone has mentioned)
Also - it looks like it was fixed in the July CTP (I mentioned that it was fixed in June, but this meant an internal version of VS)
thanks!
Fleker
DeDdY
After stating a project with June CTP and Team System I will have to reinstall everything (from team foundation, VS 2005 and SQL 2005) to start again...