Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 VA 2217 Debug Mode Very Slow in VS2017 C/C++
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

allenkk
New Member

2 Posts

Posted - Jun 13 2017 :  7:14:48 PM  Show Profile  Reply with Quote
After upgrading Visual Studio 2017 to latest version, VA becomes very slow in Debug Mode. (Already try 2217 trial)

Just try VA with my Win32 C/C++ project. In debug mode, the variables needs to take tens of seconds to display their values.
If I disable VA, the problem is gone.

Does VS 2017 latest update cause the issue?
I will try to install old VS 2017 and test it again.

feline
Whole Tomato Software

United Kingdom
18749 Posts

Posted - Jun 14 2017 :  05:19:06 AM  Show Profile  Reply with Quote
I don't recognise this problem, certainly it is not a known problem.

How many files do you have in your solution?

If you open VA's Open File in Solution dialog (Alt-Shift-O) the title bar contains two numbers. The first number is the number of files currently listed, which changes as you filter the list. The second number is the total number of files in the list, which is normally the number of files in your solution. What is this second number?

Can you also run Task Manager, and see how much memory devenv.exe is using?

zen is the art of being at one with the two'ness
Go to Top of Page

allenkk
New Member

2 Posts

Posted - Jun 14 2017 :  05:34:37 AM  Show Profile  Reply with Quote
About 100 .cpp files and 150 .h files. Not a large project.
The project works well with VA before.

The RAM of VS is normal. Not special high.
I notice that the CPU loading is high (about 25%~30% for my i7 CPU) and I can see a small progress icon keep running in VS 2017 status bar.
I use a SSD disk with 16G RAM so that I think system performance could not be an issue.

Remove all and reinstall cannot solve the issue.
I will try to setup a new PC with a whole new Windows 10 + VS 2017 then retry again.
Go to Top of Page

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jun 14 2017 :  2:53:47 PM  Show Profile  Reply with Quote
If you are able to repro please capture a va log in case it gives us any indication of the trouble. Details here:
https://support.wholetomato.com/default.asp?W305

Capturing a minidump during those tens of seconds could be useful also. Details here:
https://support.wholetomato.com/default.asp?W303
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000