While doing test execution I am facing the issue that TestComplete is getting stuck/freeze when I press play button for any tests. This issue I am facing in latest version i.e. 15.81 and it will be happening if we are using TestComplete continuously for 2,3 hours.
Has anyone also facing same issue.
Yes I am facing the same version on the latest 15.81 version. We run TestExecute and it seems to freeze as well. Eventually a 'Failed to start' error is thrown in my pipeline, but the cause is the getting stuck / freezing of TestExecute on the 15.81 version. Before that I have never seen this issue.
Am having the freeze issue as well. Had to go back a version to no longer freeze. Would consistently freeze, usually within 10-15 mins.
So, for me, using latest Chrome and Latest TC, I get the hang. Would have to delete the process and restart to get out of the freeze.
I cannot prove the latest TC v15.81.7.7 is bad with the latest Chrome - but it sure looks that way. See my post above that my customers may use the latest Chrome, hence I need a reliable tool to use on that latest Chrome version. Not me fighting the now multiple processes that both Chrome and Edge create plus TC v15.81.7.7 which is clearly not too stable, nor stops like it is supposed to immediate upon an error - setup the same way that works in TC v15,79,x,x. UGH.
It seems that the real problem lies in the tcCrHost.exe process. And the way on how TC interact with Chrome.
In my project redesign, I use exclusively Xpath and nothing else. No built-in functions of TC even the click. (I call the javascript click function on objects but the one from TC).
And this way, the project is much more stable and TC too.
Check to see in your Task Manager if you have an accumulation of TestComplete Chrome Host (32-bit) process.
Kill them and see what happens.
He had a session with Smartbear a few days ago and the told us that it looks that especially in the pipeline (we use TestExecute) sometimes processes are not "stopped" correct.
They told me to solve it and bring out a new version soon.
In the meantime they sayed we should check/and kill the following processes manually to be sure no other module is "running" when duing the tests:
Chrome, TestExecute.exe and tcCrHost.
So the reccomend to open a commandline (as Administrator) and kill the following processes via taskkill
taskkill /F /IM Chrome.exe /T
taskkill /F /IM testexecute.exe /T
taskkill /F /IM tcCrHost.exe /T
if you use TestComplete for excution you have to kill TestComplete instead of TestExecute.
But Take care when crome is running and you kill it it could be that next time there is a "recovery page popup.
So maybe just close chrome normally to avoid that or check/start chrome again after the kill and close it manually.
