IntelliSense was enabled so I disable it now.ĭebugger integration was enabled so I disabled it now.
Zen is the art of being at one with the two'ness I would have thought very unlikely with these numbers of files, but worth checking just in case.
#Visual assist 10.9 windows
Turned On or Off? This should not effect performance, but it is something that might be effecting build performance.Ĭan both of you please run Windows Task Manager in detailed view, and see what memory usage you see for Microsoft Visual Studio? Since the IDE is a 32bit process there is a 3gb limit on how much memory it can use, so its possible that you are running into this. VA Options -> Debug Assistance -> Enable debugger integration required by VA Step Filter for native C/C++
#Visual assist 10.9 code
Do you know if your build process updates / generates code files that VA might then be parsing? Martin, ending a build is not a situation I would expect VA to care about, since it does not involve editing the code files. I got the number 90 by opening the SLN file in a text editor, and searching for unique lines describing the DEBUG|圆4 state of each configuration. The test case only has a single project, but 90 different configurations. There is a known problem that shows up on solution load. Which programming language, or languages is your solution written in?Īssuming you have turned Code Inspection back on again, and that you are using C++, can you please add the following test function to a cpp file, and see if Code Inspection picks up the redundant continue and return lines:įor(int nScan = 1 nScan Options -> Text Editor -> C/C++ -> Advanced -> IntelliSense -> Disable IntelliSense = Trueĭoing this would mean you don't have to worry about both VA and the IDE parsing everything at the same time.Įdl_si, do you have a lot of projects, or Solution Configurations, or both at once, in your solution? A delay on start up suggests VA is having to do a lot of work parsing the solution structure. The second number is the total number of files in the list, which is normally the number of files in your solution. The first number is the number of files currently listed, which changes as you filter the list. If you open VA's Open File in Solution dialog (Alt-Shift-O) the title bar contains two numbers. To get a sense of scale, how many files do you have in your solution? 0 built 2021.04.23Ĭ:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Include\um Ĭ:\Program Files (x86)\Windows Kits\10\Include\2.0\cppwinrt Ĭ:\Program Files (x86)\Windows Kits\10\Include\2.0\winrt Ĭ:\Program Files (x86)\Windows Kits\10\Include\2.0\shared Ĭ:\Program Files (x86)\Windows Kits\10\Include\2.0\um Ĭ:\Program Files (x86)\Windows Kits\10\Include\2.0\ucrt Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\include Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\7\atlmfc\include Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\7\include Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\UnitTest\include Ĭ:\Program Files (x86)\Windows Kits\10\Source\2.0\ucrt Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\src Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\7\crt\src Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\7\atlmfc\src\atl Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\7\atlmfc\src\mfcm Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\7\atlmfc\src\mfc Īpologies for this problem, obviously this should not be happening. License: Standard (xxxxxxxxxxxxxx) Support ends 2022.01.28 Disabling the whole VA on the other hand seems to help, but my productivity is badly reduced. Disabling Code Inspection in VA did not resolve the issue and frozen devenv.exe was still waiting on VaCodeInspectionServer.exe (why?) and VaDbMtx.exe.
I tried "Analyze Wait Chain" from task manager and it indicated that one thread in devenv.exe is waiting on VaCodeInspectionServer.exe and another thread in devenv.exe is waiting on VaDbMtx.exe. VS (devenv.exe) does not consume any CPU when it is frozen. After freezing the VS is nonresponsive and displays "Visual studio is busy" notification.
It looks like the actual freeze is more likely to happen just after build finishes but I think it does not limit to this situation. Sometimes it freezes three times a day but sometimes it freezes five times in one hour.
#Visual assist 10.9 software
Whole Tomato Software Forums - Regular freezes of VSĪfter upgrading to VS 16.10 (16.10.2 just now) I am experiencing regular freezes of the Visual Studio.
0 kommentar(er)
