It would be, and I'm going to keep some records around it. The other problem is that "often" is a weird term in this case. I can't seem to find any pattern, and the issue doesn't seem to crop up often enough to be reproducible easily.
I was hoping to find someone with a similar issue, or at least suss out any more ideas on how to get to the root of this.
It's written in C#, and we are using WPF.
One thing is that TestComplete execution does have an overhead on the machine. So, if the machine you're running your tests on is just around the minimum recommended for your application and you add TC/TE on top, yeah, you'll have memory issues.
That could definitely be the case, and I should gather some data on the machines that have had this issue.
Hi,
I would recommend to create a Support ticket via the https://support.smartbear.com/message/?prod=TestComplete form. Support guys may ask you for the information that may help them to find the root of the problem. (Note, that SmartBear considers requests to sign NDA if your company thinks that this is needed.)
Additionally, you may consider to use the Report Generator tool provided with TestComplete (https://support.smartbear.com/testcomplete/docs/testing-with/advanced/tracing-critical-errors/report-generator/index.html) and use it to try to get the stack traces that might help your developers to find the reason of the problem internally. (I don't remember if it is explicitly described in the documentation, but it is possible to start more than one instance of Report Generator and attach them to different applications to get more than one synchronized stack traces if needed.)
