running large tests via nunit-console-x86.exe results in OutOfMemoryException
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NUnit Framework |
Triaged
|
Undecided
|
Unassigned |
Bug Description
[This issue is now being handled under Github.
See https:/
Hi,
when we're running large tests with many assemblies we get an OutOfMemoryExce
src/ClientUtili
...
else
{
foreach (TestRunner runner in runners)
if (filter.
{
try { result.
finally { runner.Dispose(); }
}
}
...
public void Dispose()
{
foreach (TestRunner runner in runners)
if (runner != null)
{
}
}
We're not sure if this could cause any side effects, but for now it helps us through. We can reconstruct this problem with a simple dummy test where memory is allocated by a big static array. Also get the OutOfMemoryExce
We're running NUnit with the pre 2.6.2 version, but the problem also occurs in release 2.6.1.
[Runtime Environment]
[OS Version: Microsoft Windows NT 5.1.2600 Service Pack 3]
[CLR Version: 4.0.30319.269 ( Net 4.0 )]
Tried also some different parameters, but running with default settings for now.
Thanks in advance.
Changed in nunitv2: | |
milestone: | none → 2.6.3 |
Changed in nunitv2: | |
milestone: | 2.6.3 → none |
affects: | nunitv2 → nunit-3.0 |
description: | updated |
tags: | added: github |
The problem I envision with your fix is that under the Gui, the runners may be needed to re-run the tests. I would expect NUnit to crash in this situation when it tried to use a runner that was already disposed.
I'm about to issue 2.6.2, so it's a bit late to spend time on this now. If you can attach your dummy program that shows the problem in a single domain, we'll try to fix it for 2.6.3.
Charlie