TestComplete 11 - memory leak (?)
Friends : This issue is with TestComplete11-python I noticed that on my machine, the testcomplete memory does not get freed up after execution. In our org, we have a UI automation framework writ...
Forum Discussion
I initially discovered the leak in 11.0 python scripting. We went through a cycle of patches and then 11.1-11.31 came along and the effect seems to be minimized FOR running suites and loading python libraries. HOWEVER, for libraries that are over 800 lines, we noticed that while we are adding new lines of code, the memory consumption bubbles up uncontrollably. We logged a support ticket which SB seems keen to fix. This is an unacceptable issue that needs to be resolved asap. We are basically on halt until this is resolved! Glad we are not the only ones reporting it though
We suspect the memory leak is also coming from the intellisence feature of TestComplete.
if the leak happens during script development :
@ Turn this off and you will notice a slight reduction in the leak.
@ During development, manually create an error and have the script debugger show that error. Continue writing yourcode.
memory leak should be reduced as well.
if the leak happens during execution :
@ Update to the latest 11.31. At least for python, execution memory leak has been significantly reduced. Not removed, but
reduced.
Other tips:
1. minimize logging to 10 log files
2. Run from Project items instead from the IDE
Thank You for the info. Trying 11.31 would be nice, but my maintenance expired, so I have to stick to 11.20 :-(
I load up two Memory usage diagrams. Both reflect the same test, the first after starting the System and TC, the second is for re-running the test with TC open.
Memory usage only knows one way: up.
There is one more curiosity occurring during "Long" test runs (> 1h):
Sometimes the Access to the Control's SystemMenu property seems to be lost, Control.SystemMenu does no more get me a valid object. Maybe this is related somehow to loosing Memory?
find attached a graphic showing the Memory usage of a sample test run in TC 11.20.
The test run repeats the same ODT test 3 times, running for 5,5h total time. The tested application is restarted for each run, as it also does have some Memory issues.
In the first run, used Memory increases constantly. At the end, TC Releases some of the Memory.
In run #2, consumption starts at a lower pace, so some of the Memory seems to be reused (good idea). But then, consumption accelerates, and one can identify how certain ODT items being processed lead to consumption jumps.
Run #3 is similar to #2.
If this application shall be used for extensive professional testing, this has to be stopped.
