TestCompleteService9 gets 99% of CPU

Hi Geeth,

You need to apply the patch Alex mentioned. Have you done this?

Hi Raul,



To help us collect information about the problem, please follow the steps below:



1. Download the Debugging Tools for Windows package from here

and install it.



2. When the problem occurs, open the "Start | Run..." dialog and execute the following command:

"C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe" -pn TestCompleteService9.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"



This command will make WinDbg write a memory dump of the TestCompleteService9.exe process to the "C:\Dump1.dmp" dump file. After the dump is written, WinDbg will be closed.



3. Correct the dump file name in the above command line (for example, change it to Dump2.dmp), wait for two minutes and execute the command again.



4. Repeat step 3.



5. Send us all of the generated dump files.



Also, please clarify whether your project contains the Network Suite node.



Thanks in advance.

Hi Lexi,



thanks for your detailed answer.

When I got this error, I have tried to obtain the information with the debugger utility but I did not have enough permissions in the company domain. I have called IT and neither do them.

Then, we should raise this to global IT service (in Switzerland) and this is not realistic because of politicals reasons.



--> Do you have a workaround to get this information?



I have created a local account in the computer, with the computer out of the domain and this error did not reproduce.



Looking in suppport, I have found this could be because of windows firewall or the working on a network distributed environment script.

This has not worked.



It is very strange but normally we found this error in the afternoon.



--> Could it happen because an internal TestComplete service procedure? Or could it be because the domain processes perform some kind of checking or ...?



--> Is this service needed once you have openede Testcomplete and load yiour project?



Looking forward to hearing from you.



Best regards,





Raul

Hi Raul,



You can try collecting additional information in the following way:



1. When TestComplete 9 Service gets the most of CPU, wait for about five minutes and run WinDbg ("C:\Program Files\Debugging Tools for Windows\windbg.exe").



2. Attach WinDbg to TestComplete 9 Service's process (File | Attach to a Process | TestCompleteService9.exe). In the Attach to Process dialog, check the Noninvasive check box.



3. Type the following command in the Command window:

.dump /m "C:\TCServiceDump.dmp"

and press Enter.



4. Wait for one minute and repeat step 3 to save another dump file with a different name.



5. Repeat step 4 two more times.



6. Send us all of the dump files created in the above steps.

Could it happen because an internal TestComplete service procedure? Or could it be because the domain processes perform some kind of checking or ...?

Unfortunately, without getting memory dumps from you, we cannot predict what is the reason for the problem.

Is this service needed once you have openede Testcomplete and load yiour project?

No, the TestComplete 9 service is not required for running TC and loading a project.

We regularly have the same problem running TC9 directly on desktop client PC

We get the same problem on all three of our test machines

Hello Pete,





Please follow the steps posted by Lexi, and send the collected information to Support.

Thanks!

Hi Lexi,



I am trying to follow your second recommendation but when I try to attach winddbg to testcomplete 9 Service, I have the following message:

            "Unable to examine process id 4472, Win32 error 0n5"



And in the bottom of window there is the message "Debugee not connected"

Should I connect previously the debug? in case I needed, how do I do it?



Thanks,



Raul

Hello Raul,





Please run WinDbg with elevated rights - right-click its executable, and select "Run as Administrator".

This helps on my Win7 computer.

Hello Alex,

I have run it with administrative rigths and I have the following messages:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path.           *

* Use .symfix to have the debugger choose a symbol path.                   *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

WARNING: Process 6956 is not attached as a debuggee

         The process can be examined but debug events will not be received

............................................................

(1b2c.a98): Wake debugger - code 80000007 (first chance)

eax=002e15e8 ebx=00000000 ecx=002e04b8 edx=00000000 esi=00000134 edi=00000000

eip=77196194 esp=0012fb6c ebp=0012fbd8 iopl=0         nv up ei pl zr na pe nc

cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\SYSTEM32\ntdll.dll -

ntdll!KiFastSystemCallRet:

77196194 c3              ret

Could you help me to identify/solve what should I configure?



Thanks,



Raul

Hi Raul,





When attaching to the process, in the "Attach to Process" window, disable the Noninvasive option - this should help.

Let me know if it does not.