Commented Unassigned: Chutzpah / PhantomJS timeout around 700 tests? [225]

Hello - I'm using Chutzpah 2.2.1.173 from the command line to automate Jasmine tests. I've been seeing strange behavior where the test run will fail after running about 700 tests (never the same number... sometimes it's more than 700, sometimes less). Here's the error from the output:

Chutzpah Error: Chutzpah.Exceptions.ChutzpahException: Unknown error occured when running c:\BuildArchive\Workspace\G2Web\WebApp\Test\ChutzpahTests.html
at Chutzpah.TestRunner.HandleTestProcessExitCode(Int32 exitCode, String inputTestFile) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 217
at Chutzpah.TestRunner.InvokeTestRunner(String headlessBrowserPath, TestOptions options, TestContext testContext, TestRunnerMode testRunnerMode, ITestMethodRunnerCallback callba
ck) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 200
at Chutzpah.TestRunner.<>c__DisplayClass2.<ProcessTestPaths>b__1(PathInfo testFile) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 143
While Running:c:\BuildArchive\Workspace\G2Web\WebApp\Test\ChutzpahTests.html

Here's my command line call:
chutzpah.console.exe ChutzpahTests.html /timeoutMilliseconds 800000

I also tried upgrading Chutzpah to version 3.1.1, but I get the same failure.

Am I hitting some sort of limit to the number of tests that I can run at once?

Thanks,
Keith
Comments: The issue doesn't seem to be based on the number of tests, but instead on the amount of memory that PhantomJS eats while running the tests. If I watch Windows Task Manager while running the test suite that fails, phantomjs.exe gets up to about 750,000 K for memory, then crashes. I've seen in the phantomjs documentation that memory can be deallocated by calling page.close() or page.release() ... I don't see that Chutzpah does this in chutzpahRunner.js or jasmineRunner.js ... are there Chutzpah command-line settings that would change the way phantomjs manages memory?