CVI2019 awfully slow on single step debugging

[IEE_newsoft]

Since I moved from CVI9.0.1 to CVI2019, I had to recognize that debugging into my code in single steps became a mess. Sometimes jumping from one line of code to the next one takes up to 1s, especially if watch variables have been set. And this is not due to eventual function calls. Doing exactly the same with CVI 9.0.1 is much more faster. Are there any environment settings that might affect the performance here?

Did anyone else recognize this as well?

Thanx and Regards

Manfred

[gdargaud]

Yeah, I noticed that debugging is slow. And the editor itself is slow (I can sometimes type 10 whole characters before they begin to appear on screen). And you are right that using watch variables makes the whole thing a LOT slower (it's always been the case though).

[IEE_newsoft]

Hi gdargaud,

thanx for your confirmation, nice to hear that I'm not the only one complaining! 😉

To me it now looks in CVI having a good old 486DX2/66 CPU instead of an i5..lol

You're right that using watch variables also slowed down the performance since ever (especially on list types or big arrays....by nature), but on primitive data types this is a no-go and I really see the difference in comparison to CVI9.0.1!

Maybe people that grew up following all releases since then do not notice it, but for me doing a hard cut, it cannot be argued away.

Regards

Manfred

[IEE_newsoft]

..any comments from NI regarding this?

[scottrod]

I've gone back to CVI 2017 due to editor changes in CVI 2019.

I tried my best to adapt to CVI 2019 and used it for weeks, but in the end I just couldn't work efficiently in that editor. Gave up and went back to 2017 a few months ago.