Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Technical Support

VS2015 / VAX2094 never gets ready/full CPU usage

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
lac	Posted - Apr 03 2016 : 10:56:45 AM Symptom: devenv.exe balloons to 1.2Gb RAM, stays at 12.5% CPU load (1 CPU core). Visual Assist never gets ready (never recognize any symbols). 'Open File in Solution' just says "Parsing...". Checking with Procmon (SysInternals), devenv.exe is repeatedly calling CreateFile/QueryBasicInformationFile/CloseHandle on all my include directories. It repeats this continuously, looping though all the include directories over and over, several times a second. I've tried these combinations; VS2015 Update 1 + VAX 2089 VS2015 Update 2 + VAX 2089 VS2015 Update 2 + VAX 2094 I've tried clearing the cache and rebuilding symbols via VAX options. Still same issue.
3 L A T E S T R E P L I E S (Newest First)
feline	Posted - Apr 04 2016 : 09:52:58 AM Thank you for the update. That was nasty, and it does sound like a corrupt file somewhere in the Build directory. Hopefully this will stay fixed, especially since I am not seeing anything strange or suspicious in your about information.
lac	Posted - Apr 03 2016 : 3:59:34 PM [solved] I eventually deleted the entire build directory and recreated it (CMake based). That resolved the problem. devenv.exe is sitting comfortably at 460 Mb now, and <1% CPU load. First, I deleted the .SDF and .DB files (MS switched to the .DB format in Update 2 I think). Didn't help by itself. VS bounced to 2Gb+ and ran out of memory: http://imgur.com/ncRwpqE :-) License: --------.dk (25-user license) Support ends 2016.03.03 Trial extension mode VA_X.dll file version 10.9.2094.0 built 2016.03.25 DevEnv.exe version 14.0.25123.0 Professional msenv.dll version 14.0.25123.0 Comctl32.dll version 6.10.10586.0 Windows 10 10.0 Build 10586 8 processors (x86-64, WOW64) Language info: 1252, 0x406 Platform: Project defined Stable Includes: C:\Program Files (x86)\Windows Kits\8.1\Include\winrt; C:\Program Files (x86)\Windows Kits\8.1\Include\shared; C:\Program Files (x86)\Windows Kits\8.1\Include\um; C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include; Other Includes: Stable Source Directories: C:\Program Files (x86)\Windows Kits\10\Source\10.0.10240.0\ucrt; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\crt\src; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\atl; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\mfcm; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\mfc;
feline	Posted - Apr 03 2016 : 1:23:23 PM That is really odd. As a first step, can you please try closing VS2015, and then finding and deleting the .SDF file in the root directory of your solution. This file holds the IDE's intellisense database, and will be rebuilt by the IDE. I have occasionally seen a corrupt file cause strange problems, so perhaps it is a factor here. If this does not make any difference, can you please try making a new, default C++ solution, and see if VA is able to finish parsing this solution. I am trying to find out if this is a solution specific problem or a machine problem that effects all solutions. If the problem is solution specific can you please open the problem solution, then go to: VA Options -> System Info -> Copy Info... and paste the about information into your reply. I am mainly interested in the stable include directories, since this sounds like it might be a factor.

Snitz Forums 2000