We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Forum Discussion
TestComplete 11.0 - Memory Issue
Environment Details: Windows 7, 64 Bit, 8 GB RAM TestComplete 11.0 Project Details: Used NameMapping Approach Defined All object references in one script file as Global Variables. There are ...
We are using name mapping on a 64-bit machine with 16GB of running TC 11.30. We are unable to run our entire test suite without before tcHost.exe usage grows to 1.9gb and TC locks up. If a few items are disabled the test will run all they way through. I've nearly reached the end of the road here.
Ran into a similar issue with our scripts.
I would suggest https://support.smartbear.com/message/?prod=TestComplete.
It's been a while since I've run into problems like this. However, IIRC, part of it has to do with how much information you're writing out to your test log. If you're calling Log.Message for every little thing or if you're not using https://support.smartbear.com/viewarticle/71442/?q=Log.LockEvents#_ga=1.31543550.13338051.1455026999 in your code, I think that a good bit of what you might be dealing with is that TC has to store a lot of the logging information in memory. Take a look at optimizing your utilization of the logging, reduce the number of messages, and make sure that Log.LockEvents is in place to prevent too much information being written out.
tristaanogre wrote:It's been a while since I've run into problems like this. However, IIRC, part of it has to do with how much information you're writing out to your test log. If you're calling Log.Message for every little thing or if you're not using https://support.smartbear.com/viewarticle/71442/?q=Log.LockEvents#_ga=1.31543550.13338051.1455026999 in your code, I think that a good bit of what you might be dealing with is that TC has to store a lot of the logging information in memory. Take a look at optimizing your utilization of the logging, reduce the number of messages, and make sure that Log.LockEvents is in place to prevent too much information being written out.
I'll try locking the log to see if this fixes the problem. In all the discussions with support on this issue this was never mentioned. Makes complete sense to me. Thanks.
- Hope that it helps. I'm not sure how correct I am in this but I know that logging is a big memory hog for TC in previous versions. Let me know if this helps and, perhaps, this is a memory optimization thing that SmartBear can work on for future versions.
