There have been some postings about increasing memory used by TestComplete / TestExecute.
At the moment when running a testscript by using TestExecute, memory increases by about 350KB per second. As this testcase takes some time (> 30 min), sooner or later my application under test runs out of memory.
I have little Log.Message-calls, have added Log.LockEvents(20) at the beginning and do not have any bitmap-checks.
I do not have any recursions in my function calls within the test.
To make sure that the memory usage increase is not related to the log size, add the following line at the beginning of your test:
<font class="small">Code:</font><hr /><pre> Log.Enabled := False; </pre><hr />
Run your test and look at the statistics of the memory usage. If the results are the same, try disabling the extensions you do not need - leave only those you need to keep your test working. Post your results here.
I disabled the log and disabled all extensions that I did not need.
Still the result is the same - the TestExecute memory increases by about 370K per second.
I had a look at similar tests that run against this application. Their memory increase is about 80K per second - that's little enough for the test to complete with sufficient free memory.
But the other test is not able to complete - TestExecute terminates itself after some time (in my last test run it took 11 minutes until TestExecute terminated).
I am using several quite big arrays in my tests (in both I did compare). Might there be some source of these increasing memory usage?
It looks like a memory leak indeed. To investigate the problem we will need to reproduce it in our lab.
Is it possible for you to send us your tested application along with your test? Please contact us regarding this matter by using the following web form: http://www.automatedqa.com/support/message.asp