Hi, our solution has around 2500 individual tests, and being service oriented we mock extensively. When we run all tests, we see the memory climbing and climbing, and it doesn't actually drop until the tests all finish. I just enabled multi-threading for our tests to make them run faster. This meant I had to modify RhinoMocks slightly as it isn't thread safe.
Running 4 processes has exacerbated the problem, and now, when the RAM usage hits the top of my physical RAM, the tests stop running. I have seen an old thread here: http://osdir.com/ml/windows.devel.dotnet.rhino-mocks/2006-02/msg00046.html This could explain what we're seeing, namely that RhinoMocks is "leaking" assemblies. We typically use the static MockRepository methods for creating mocks and stubs. Has anyone seen this? If so, how did you get around it? Thanks, Tim Haughton -- You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en.
