Whenever I have Visual Assist running on my new computer, the memory use of devenv.exe balloons (typically to 1.7 Gigs or so) and everything runs slow. Anyone seen this before? Is there a known solution?
Which version of VA are you using? Which IDE are you using? Which language are you programming in?
We have had a few reports of things like this when the parser is confused by your code. If the parser ends up in some form of infinite loop then nasty problems can occur.
VA_X.dll is file version 10.3.1559.0 (built 2007.07.06)
IDE is Visual Studio 2005, version 8.0.50727.762 (though I had an earlier version of VS which was also breaking which I updated to the service pack in hopes of fixing the problem).
Latest version of VA, that eliminates all of the fixed bugs.
How long does the problem take to show up? If you just load the IDE and load your solution what is the memory usage like? Does it jump to these sort of levels instantly? Take 20 minutes? 6 hours?
If you open the OFIW dialog the title bar shows two numbers, the current number of files in the list and the total number of files in the list. What is the second number? I am wondering how large your solution is. If it is *really* large it is possible this memory usage is reasonable.
Do you have any small solutions that you work with? I am wondering if the problem is solution specific.
It was typically jumping in about 5-10 minutes or so. I've since uninstalled and reinstalled Visual Studio (and the 360 SDK). Devenv.exe seems stable now although stable at 780M (other people on the project are seeing 250M). (OFIW lists 2816 files). Regardless, the memory leak seems to be gone, and enabling/disabling Visual Assist doesn't have a major impact on performace anymore, so I'm guessing my remaining problems are Microsoft's fault...
Memory Leak with VA X
Posted - Sep 06 2007 : 7:36:34 PM
