Out of Memory Exception on NUnit Version 2.2.9
Stacy Rippey <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <OF00C4A580.EA723731-ON85257472.0042AC3E-85257472.00438E50@progressive.com> |
I wanted to take the time to thank you for responding to my Out of Memory Exception Issue. A couple of us here at Progressive took initiative to clean up a lot of our code, by disposing objects & setting them equal to null at TestFixtureTearDown. We also did considerable refactoring. By doing so, it freed up a tremendous amount of memory, & NUnit even runs 5 minutes faster! It was truely poor programming on our part, & lack of knowledge on how NUnit works. Now that our test platform is stablized, I will see if our team can upgrade to a more rescent version of NUnit. Thank You! Stacy Rippey Progressive Insurance Policy Pro UI NW: 575.9501 PH: 440.395.9501 Message: 4 Date: Fri, 23 May 2008 16:06:44 +0200 From: "Charlie Poole" <[email protected]> Subject: Re: [Nunit-users] Out of Memory Exception on NUnit Version 2.2.9 To: "'Kelly Anderson'" <[email protected]>, <[email protected]> Message-ID: <004201c8bcde$3d9efb90$8000a8c0@ferrari> Content-Type: text/plain; charset="us-ascii" On the other hand, NUnit 2.2.9 is now 18 months old with 9 production releases since, so it wouldn't hurt to try the current 2.4.7 release. Charlie > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of Kelly Anderson > Sent: Thursday, May 22, 2008 12:15 AM > To: [email protected] > Subject: Re: [Nunit-users] Out of Memory Exception on NUnit > Version 2.2.9 > > The last time I saw this it was a stack overflow in my own > code. Have you attached a debugger to the process and seen > where things go wrong? > > Updating NUnit probably won't help if that is the problem. > > -Kelly > > On Wed, May 21, 2008 at 1:23 PM, Stacy Rippey > <[email protected]> wrote: > > > > Hello! > > My team is experiencing an OutOfMemory exception while > running NUnit > > Tests on Version 2.2.9. > > > > We do initially load a lot of information, but I can't seem to > > pin-point the best approach to dispose of the data after > each TestFixture is run. > > > > I did a lot of research on the internet & did not come up with the > > best approach to fix this. > > > > I was wondering if any updates have been made to NUnit that could > > help us out? > > > > Our Exception: > > > > NUnit Exception: > > > > System.OutOfMemoryException occurred > > Message="Exception of type 'System.OutOfMemoryException' > was thrown." > > Source="mscorlib" > > StackTrace: > > at System.IO.MemoryStream.set_Capacity(Int32 value) > > > > This is a website noting the very same issue that we are having: > > http://osdir.com/ml/windows.dotnet.nunit.user/2007-06/msg00016.html > > > > Thank You! > > Stacy Rippey > > Progressive Insurance > > Information Technology > > PH: 440.395.9501 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php