2

Resolved

OutOfMemoryException in large solutions

description

I Installed the tool today and I really liked it but as soon as I tried to load a large solution (109 projects) VS2008 Pro SP1 crashed with a OutOfMemoryException. I tested with different solutions on different machines and same result. As soon as the solution is large it takes forever loading and VS crashes before seeing the end of it. Seems like a memory leak...

comments

Avatar78 wrote Dec 2, 2008 at 2:53 PM

We use this NUnitForVS on several PC's and all get OutOfMemoryException after a while. We also see that under the directory: %TEMP%\nunit20\ShadowCopyCache a huge amount of directories is stored.

On each build X directories are added to this temp path. The amount X is equal to the number of projects in your solution. Under these new directories you find the dependencies used by the unit testing project.
So in my solution are 24 projects, so each build generates 24 new directories which are never cleaned up. And all assemblies of each build stay loaded in memory until you shutdown visual studio. So the memory usage grows until all memory is used. In my case the memory used by visual studio then grows to about 800MB and then I run out of memory.

Can you look into it this and free/unload and delete al unused assemblies from these temp folders from all previous builds?
An example of temp path is: C:\DOCUME~1\user\LOCALS~1\Temp\nunit20\ShadowCopyCache\633638059465283626\Tests\assembly

This would really help us.

Our setup:
Windows XP SP3, Visual Studio Pro 2008 SP1, NUnit v2.4.8, NUnitForVS from 13july2008

wrote Dec 2, 2008 at 2:55 PM

wrote Jul 23, 2009 at 9:26 PM

A lot of loading and reflection has been removed. This should result in less memory consumpyion. Do however note that mstest contains a full test list. This memory usage, we can't improve on.

wrote Aug 10, 2009 at 3:59 PM

wrote Aug 10, 2009 at 3:59 PM

wrote Feb 14, 2013 at 3:16 AM

wrote May 16, 2013 at 8:59 AM

wrote May 16, 2013 at 8:59 AM

wrote Jun 14, 2013 at 7:55 AM