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

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.