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

Forum Discussion

Ryan_Moran's avatar
Ryan_Moran
Valued Contributor
10 years ago

Ran into a similar issue with our scripts.

I would suggest https://support.smartbear.com/message/?prod=TestComplete.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
10 years ago

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.

  • william_roe's avatar
    william_roe
    Super Contributor
    10 years ago
    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.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      10 years ago
      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.
      • william_roe's avatar
        william_roe
        Super Contributor
        10 years ago
        tristaanogre wrote:
        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.

        I'm confused about something. Wrote the following function and passed 'true' and 100 and yet the logs shows more than 100 entries (see image). What am I missing?

         

        function LockLog(val, count){
    if(val == true)
        Log.LockEvents(count);
    else
        Log.UnlockEvents();
}