Memory bloat when using Visual Studio

Visual Studio 2005 has been taking up 600MB+ of memory, with a VM footprint around the 1200MB mark. I thought it might have been a plugin I use, Visual Assist, but I’ve uninstalled it and still have this problem. It will happen with normal use, but happens much quicker if I attach/detach the debugger to an application a few times. Anybody have any thoughts on what might be causing this

Answer this question

Memory bloat when using Visual Studio

  • eldiener

    You can use a performance monitor to determine if you are thrashing. I am not sure of the exact items, but you want to monitor page ins and outs.

  • Prabu.

    Thank you both for your replies.

    I have looked at some articles on TechNet that were related to memory thrashing, though none of them were all that useful in my situation. Neither of the hotfixes pertain to my situation either, since I do not do any Web application developement. I did try to reinstall VS 2005 SP1 though, but that didn't change anything. For kicks, I also deleted my NCB and SUO files, since that has solved some problems I've had with VS in the past but didn't fix this problem.

    I did resolve this problem by "disabling" intellisense. Intellisense seems to have several known issues pointed out in this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=132651&SiteID=1

    I disabled intellisense by creating a directory with the same name as the ncb file that it would create, stopping it from creating that file. Visual Studio now works wonderfully, even with Visual Assist. If there is any information I can get to help fix any problems with intellisense, please let me know, and I would be happy to help.


  • Rocinante8

  • Sue Mosher - Outlook MVP

    Windows uses virtual storage extensively to relieve requirements for real storage. Issues of use of memory are more complex than mot people realize. The important thing is thrashing; does Windows have enough real storage. You can find articles about such things in the TechNet site and many other places.

  • Memory bloat when using Visual Studio