#Visual assist whole tomato move line software#
#Visual assist whole tomato move line code#
#Visual assist whole tomato move line plus#

'The file was never intended to be user-editable' I see that VSWorkspaceSettings.json was removed from docs in this PR from June 2019.

#Visual assist whole tomato move line plus#

On 2393, Open File in Solution was reporting 0 out of 0 files up to the point of crashing (I was opening it then closing periodically after VAX's 'Reading solution projects.' message box came up then went away).ДЄs for how large my directory tree is, this is what I have mapped down from Perforce (this is going to include build artifacts and such, plus a chunk of game-ready data for a couple of games): Even though I had 'Automatically check for new version' enabled, 2393 wasn't notifying me there was a new version for some reason. I'm noticing now that 2399 is out so I'm in the process of getting that and will attempt to repro the issue again. Zen is the art of being at one with the two'ness So it makes sense that VA is doing some parsing of all of these files and directories, exactly as the log suggests. VA's Open File in Solution dialog not respecting the ExcludedItems setting defined in VSWorkspaceSettings.json is a known bug: I am also wondering if this is anywhere near the size of your directory tree. SLN file, that holds 94,000 files, but since this uses a SLN file, and it probably does not have as complex a directory structure, I am not sure how well it compares to your situation. Which version of VA are you using? VA 2393 introduced several changes to try and reduce our memory usage with large solutions, so if you are using an older version it is worth trying the current version to see if any of these changes help.ДЄre you able to load this directory / CMake project with VA enabled long enough to use VA's Open File in Solution dialog to get a count of the number of files VA thinks are in the 'solution'? I have a large test solution, an actual. This does indeed sound like an out of memory problem. Which is annoying to (remember) to do, but also means I'm left without my VAX-based Intellisense/code highlighting safety blanket. Given all of this, whenever I want to work in the CMake project, I currently have to disable VAX altogether.

This doesn't result in a crash, because it doesn't automatically enumerate the project to gather intellisense data upon re-enabling. However, with this crash with VAX enabled there's no dump generated.ДЄnother thing I tried was first disabling VAX, opening the project folder, then re-enabling VAX with the folder still opened. For most other crashes in VS2019, I get a. I suspect that since CollectFolderProjs isn't ignoring the sub-projects/folders we list in 'ExcludedItems' that it ends up not only wasting cycles enumerating those folders, but is allocating memory from those scan results and the crash itself may be an OOM.

#Visual assist whole tomato move line code#

These sub-projects include not only code (still on sln/vcxproj) but GBs of tools and source content in thousands of folders (they're individual games).

So their root sub-folders are in 'ExcludedItems'. However, there are many sub-projects (in sub-folders) which are *not* part of the CMake setup. Our project's root folder has a CMakeList.txt, and so the process is to open the root. This is what we change to make VS not populate folders or file patterns in the solution explorer. I suspect the problem relates to CollectFolderProjs not respecting the 'ExcludedItems' array in VSWorkspaceSettings.json. Inspecting this file, there's an enormous amount of CollectFolderProjs logs (231013 instances), including the last line itself. I enabled logging in VAX and ended up with a 21.7MB va.log file. Usually around 2785MB or so (since VS2019 is 32-bit, this suggests to me a possible OOM)

With VAX enabled, I can watch VS2019 continue to grow in Task Manager until it ends up crashing. With VAX disabled, VS2019 sits at around 800MB of used memory with this project open and idle. Ever since then, when I open the project's folder in VS2019, it will eventually crash soon after when I have VAX enabled.

#Visual assist whole tomato move line software#

Whole Tomato Software Forums - VS2019 CMake+VAX issuesДЄ project at work switched to CMake last year.