Forum Discussion
I'm not seeing where in that stack trace anything specifically implicates TestComplete. If this is showing in your application logs, then there's something in your application that is consuming memory.
Now, it COULD be TC's interaction with it... but without more information, it's hard to say.
Yeah, I'm not fully convinced either, but I'm trying to figure out some way to get to the root issue.
The dev I'm working with is fairly confident in this being an issue with TestComplete (though he's biased against it).
I also keep running into the problem that this only seems to happen when TestComplete is running the application.
- tristaanogre7 years agoEsteemed Contributor
It would be interesting to know if there are particular parts of your test case where this happens regularly.
I'm assuming it's a desktop application... what technology is it written in (Delphi, C# .NET, etc)?
- cmpenn7 years agoContributor
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.
- tristaanogre7 years agoEsteemed Contributor
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.
Related Content
Recent Discussions
- 3 days agovladd1