Does it always run slow or is it an intermittent problem?
Is it always the same test or does it run slow in different places?
Have you checked to make sure that you don't have more than one copy of your application running?
Do you have other applications running on the same machine that you don't need for testing?
This seems to happen particularly when accessing the name map, or on the name map. It's intermittent elsewhere.
Does TestComplete freeze when you open the name mapping or does it take a while to open? How long does it take to open?
Viewing the name map seems fine, but if I try to edit a mapped object, (even right-clicking it), the whole program is down for the count. I wait several minutes (3+) before it's usable again. The same thing happens if I attempt to use the "highlight on screen" from the name mapping view.
Let's try this. In Name Mapping Options dialog, select Tools | Options from the main menu and then select Engines | Name Mapping. Turn off "Search for visible objects first" and try again.
https://support.smartbear.com/viewarticle/80481/
Search for visible objects first - This option tells TestComplete to prefer visible over invisible objects when searching for mapped objects. If it is enabled (by default), TestComplete first tries to find a matching object that is also visible. If a visible object is not found within the search timeout (Auto-wait timeout or the timeout used in WaitAliasChild), TestComplete picks any invisible object that matches the mapping criteria.
If this option is disabled, TestComplete always picks any matching object, whether visible or not.
Notes:
Disabling this option can reduce the object search time in tests that deal with many invisible objects.
This option has no effect for objects whose mapping criteria explicitly include the Visible property.
If you upgraded from TestComplete 10 to version 12 and found that your tests became slower, disable this option.
