Hello Ivan,
To help us investigate the issue, please follow the instructions below:
1. Disable the debugger in TestComplete and check whether the issue persists. To disable the debugger, you need to uncheck the Enable Debugging item on the Test Engine toolbar or in the Debug menu.
2. Try disabling TestComplete's OpenApps plug-ins and check whether the issue persists.
Here is the list of the OpenApps plug-ins:
- .NET Open Application Support
- Delphi and C++ Builder Open Applications Support
- Java Open Application Support
- JavaFX Open Application Support
- MSAA Open Applications
- Microsoft Visual C++ Open Application Support
- Open Applications Support
- Qt Library Support Plug-In
- Silverlight Open Application Support
- Visual Basic Open Applications
To disable the plug-ins, select File | Install Extensions from the TestComplete main menu, in the ensuing dialog, uncheck all the plug-ins you want to disable and click Ok.
3. If there are event handlers in your project, please disable them as well and check whether the issue persists.
Also, could you please send several dump files to our Support Team? To do this, please follow the instructions below:
1. Download the Debugging Tools for Windows for 32-bit process or Debugging Tools For Windows for 64-bit process package and install it.
2. When TestComplete hangs when running the script, open the Start | Run dialog and execute the following command:
"C:\Program Files\Debugging Tools for Windows\windbg.exe" -pn TestComplete.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"
This command will make WinDbg write a memory dump of the TestComplete.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. Use
this web form to send all the generated dump files to our Support Team.
Thanks in advance.