Forum Discussion

jkrolczy's avatar
jkrolczy
Super Contributor
1 month ago

TestComplete Chrome Host (32-bit) process not clearing up after running test

I am using TC 15.81.7.7

I am checking to see if other have been seeing the issue where after running Chrome web testing, where trying to run the next test script manually, TestComplete hangs.

I can go in the Tasks manager and see a lot of these:

TestComplete Chrome Host (32-bit) process

If I start to kill them, I eventually get TestComplete to continue with running my hung script.

So asking if anyone has seen this and maybe sone cleanup code in place you use after you script

runs.

Just for clarification,

When a test script is run using Chrome, you should see only one of the processes in Task Manager ?

TestComplete Chrome Host (32-bit) process

And once the test script completes, this process should going away, or stay ?

 

Thanks

2 Replies

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    1 month ago

    I'm using TestComplete v15.80.1.7 and I noticed this morning, there were a number of issues relating to PKCE authentication, and it's also taking longer for TestComplete to launch.

    Looking at the history of TestComplete v15.81, they seem to have fixed an issue relating to TC-108983 Resolved an issue that caused automatic reauthentication in PKCE scenarios after closing the login window.

    I'm wondering whether they have broken something!

    Only one instance should exist
  • amy312james's avatar
    amy312james
    New Member
    1 month ago

    Yes, others have seen this behavior—TestComplete sometimes leaves behind multiple “Chrome Host” processes after running tests, which can cause hangs when starting the next script. Normally, you should see just one process during execution, and it should terminate once the test finishes. If it lingers, cleanup may be needed: many teams add teardown code to explicitly close the browser at the end of each run, or use Browsers.Item("chrome").Close() in their scripts to ensure TestComplete releases the process before the next test starts.