Environment Details:Windows 7, 64 Bit, 8 GB RAMTestComplete 11.0 Project Details:Used NameMapping ApproachDefined All object references in one script file as Global Variables.There are 3000+ Variables.Reading and Writing Data from Excels Problem:When i open my project. RAM usage is 320-340 MBWhen i run any of my test function RAM usage will increase to 450-500 MBIf i keep on running test functions RAM usage will increase to 800+ MBThis is making my test execution go slow and crashing application under test.Anybody faced this kind of issue ?Why RAM usage will be increasing every time ?Is there any memory leakage ?Why after execution RAM usage is not coming to normal ?

Defined All object references in one script file as Global Variables.There are 3000+ Variables. What is the purpose of doing this? It probably isn't causing the memory issue you're facing, but it seems redundant and unnecessary if you know how to use NameMapping properly. As for the memory issue, can't say I have the exact same problem as you, but I used to notice TestComplete would use more and more RAM if I was using it over the course of a day or two without restarting it. I eventually came to realize that the SQL DB connections I was opening weren't always being closed because the test script would sometimes be interrupted and the code to close the connection wouldn't be executed. So if you are opening DB connections or files or anything else that could lead to a resource leak I'd suggest trying to make your code more robust to ensure any open resources are closed. I used the OnStopTest event to close any open connection I might have.

Well there doesn't look to be an error or warning so there should be 0 events in your log. The 100 only says to hold onto the last 100 events and put them in the log if an error or warning occur. That's how it works for me at least. Seems like something must be going wrong with your function or maybe the call to your function. I'm not very familiar with JScript so I can't say for sure, but maybe try adding a Log.Message() within the if statement to see if it's actually reaching the Log.LockEvents() call.

That's strange. Property checks, certainly, aren't events. But clicks and keyboard inputs are events. Now, I'm running TestComplete 10.60 on my end but I can't imagine the code has changed that drastically. Here's what I did. And the result is that without that Log.LockEvents call, the click event is showing up in my log. With it, though, I no longer see the event I did a bit more experimentation... and I reproduced your problem. In looking at the screenshot you showed, I see all your Keyword tests executing but I don't see where you are calling "LogLock" so I'm still not certain how you are calling that. But your log screenshot shows that each keyword test is a different test item in your project. The Log.LockEvents function only affects the current test item. So, if you have two test items and you call LogLock in the first test item but not in the second, the events will be locked for that first test item but not for any of the others. So, here's what I did. I took your function and put it in a script code unit. I then created an event handler for the OnStartTest event. That event handler calls your LogLock function

So, that new keyword test is in a test item. WIthout the event handler in place, when that test executes, here's the log With the event handler in place, here's the new log Hope this helps

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.

TestComplete 11.0 - Memory Issue | SmartBear Community

william_roe
Super Contributor
9 years ago
I've added steps to logout out of the application, close and re-open the browser and login into the app prior to the point the memory causes to the test to crash and this seems to work.. This workaround allows the test complete. I've opened numerous tickets the memory problem.
william_roe
Super Contributor
9 years ago
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.
- dganov
  Staff
  9 years ago
  william_roe, you wrote: "We are unable to run our entire test suite without before tcHost.exe usage grows to 1.9gb and TC locks up". I am curious what is tcHost.exe? I failed to find it in my TestComplete folder.
  - william_roe
    Super Contributor
    9 years ago
    dganov wrote:
    william_roe, you wrote: "We are unable to run our entire test suite without before tcHost.exe usage grows to 1.9gb and TC locks up". I am curious what is tcHost.exe? I failed to find it in my TestComplete folder.
    tcHost is a process spun up in memory when TC is running. We get somewhat frequent crashes from this process.
- Ryan_Moran
  Valued Contributor
  9 years ago
  Ran into a similar issue with our scripts.
  I would suggest contacting support.
  - tristaanogre
    Esteemed Contributor
    9 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 Log.LockEvents 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.
ghuff2
Contributor
9 years ago
Defined All object references in one script file as Global Variables.
There are 3000+ Variables.

What is the purpose of doing this? It probably isn't causing the memory issue you're facing, but it seems redundant and unnecessary if you know how to use NameMapping properly.

As for the memory issue, can't say I have the exact same problem as you, but I used to notice TestComplete would use more and more RAM if I was using it over the course of a day or two without restarting it. I eventually came to realize that the SQL DB connections I was opening weren't always being closed because the test script would sometimes be interrupted and the code to close the connection wouldn't be executed. So if you are opening DB connections or files or anything else that could lead to a resource leak I'd suggest trying to make your code more robust to ensure any open resources are closed. I used the OnStopTest event to close any open connection I might have.

Forum Discussion

TestComplete 11.0 - Memory Issue

Related Content

TestComplete 12 - memory leak (?)

Issue with TestComplete COM object loading

Do not see fake memory leak in a DLL

"Interactive user session" issue with TestComplete and Jenkins Integration

TestComplete issue with recognizing objects using object spy.

Recent Discussions

Support for Windows Server 2022

Chrome Blocking iocm.js Upon Microsoft OAuth Login Attempt

TC/LoadNinja Integration Databanks?

How to stop TestComplete from failing a test when unrelated processes crash?

Performing select all and delete on BitBar iPad or Android device