Hi,
I have start using VS 2005 this week and i notice that when i am using the step over while debuging it is response very slowly compered to VS -6.
I notice that the call stack and Autos windows also addes to the poor performance, and each step the auto windows refresh.
10xs alon
Step over (F10) responds slowly
Somebody
Sorry but it didn't help.
Bono not!
Hi,
I know that every step the autos window are refresh and load the old/ new value of the variable.
1) At VS-6 when you debug (pressing F10 rapidly) the call stack and the other watch windows (include local, auto) was update without flickering and you not see the refresh , now at VS 2005 every step or more (when the autos/ local windows need to reload the current variable) you get flickering for 1-2 seconds, and also the CPU reach to 100%.
2) Intel Pentium 4, 3.2 GHz, Memory 2G, OS windows XP SP2
3) The project is a local code - Native.
4) The project at quite big, include 1500 files of C/C++, the same project works fine at VS-6, i have notice that in VS-2005 it is possible to watch STL (vector/ map) variable at the debug, maybe this take time & CPU in order to recalc every step.
10xs
Epicycles
Please take a look at our debugger FAQ at http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=919407&SiteID=1. There are some steps you can take to help us determine what the problem might be.
Because this thread is so old, I'm going to mark it as answered. Please feel free to reactivate with further details.
Sevana Oy
If you set this option:
Tools/Options/Debugging "show raw structure of objects in variables window"
you'll be able to see if your perf is lost rendering your STL objects in the auto's window.
Anika
JordanBean
The autos window has always refreshed on every step, and performance has always been affected by what Windows you have open.
Can you be more specific about what you are seeing:
1) What do you mean by 'poor' performance 1/10 second per step, 1 second per step, 10 seconds per step
2) What kind of hardware do you have
3) What kind of code is this (Managed/Native/Script/SQL)
4) What is your scenario