locked
VS 2008 Unit Test painfully slow after installing SP1 RRS feed

  • Question

  • We are developing in C# .Net Framework 3.5Sp1.

    After installing SP1 for VS2008 our Unit Tests are running painfully slow on all of our machines (Win 7 Ultimate 64bit, Core i3 & Core i5 4Gb Ram).

    Before Sp1 we ran for example about 600 Tests in 2-3min and now it takes up to 20min. Even very simple Test like "get all items from DB" are slowed down by factor 3-5 when exectuted as a single test.

    Additionally we sometimes are experiencing Out of memory Exceptions if all tests are run and so on some machines it is not possible to run the tests any longer. But before SP1 everything was alright.

    While trying to finde a solution we came acroos these artciles:

    http://social.msdn.microsoft.com/Forums/en-US/vststest/thread/3e9cb0e1-3140-4854-99d3-904f4974a52d/

    http://confluence.jetbrains.net/display/ReSharper/OutOfMemoryException+Fix

    http://stevenharman.net/blog/archive/2008/04/29/hacking-visual-studio-to-use-more-than-2gigabytes-of-memory.aspx

    But nothing seems to be working.

    Is there any Hotfix we are missing?

    We already installed KB957912 due to the Breaking Bug we experienced. But with these painfully slow we are currently thinking about re-installing VS 2008 again und just don't update to SP1, but actualyl this can't be a really practical solution.

    edit:
    sometimes it is also nearly impossible to view Test Details. Before SP1 when you clicked on test Details they showed up in just a few seconds. Now we have to wait for 30-60seconds. And if we try to export all Test Results we always get an Out of memory Exception.

    Please Note that 2 of the machines we are working with are completely new. So this strange behaviour happend just after installing the OS, installing VS, getting all Updates and then installing SP1. 


    Friday, August 19, 2011 8:01 AM

All replies

  • We now just switched back to VS 2008 without the SP1 and everything is running smoothe again.

    Maybe this is going to be fixed someday...

    Wednesday, August 24, 2011 5:44 AM