Forum Discussion
Hello Michael,
We've been unable to reproduce the behavior here.
There is a chance that the issue is caused by some exception in TestComplete. To check this assumption and trace the exception if the assumption is correct, please use AQtime Standard, our free profiling tool. AQtime can trace exceptions and show their call stack. Data generated by AQtime can help our developers find the cause of the problem.
Here are the steps:
1. Download AQtime Standard
2. Install the tool.
3. Start AQtime with the -NotOpenApp command-line argument. For example, you can use the following command line:
"c:\Program Files\SmartBear\AQtime 7\Bin\AQtime.exe" -NotOpenApp
4. Select the 'File | New Project From Module...' main menu item.
5. In the Open File dialog, select the TestComplete.exe file and click Open.
6. Take a look at the AQtime toolbar - there is a combo box. Open it and select the "Tracing | Exception Trace Profiler" item.
7. Select the "Options | Options..." main menu command - the Options dialog will appear.
8. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.
9. Click the Run toolbar button (the green arrow) or press F5 to start the profiling.
10. AQtime will start TestComplete and trace all exceptions that will occur in the application until it is closed.
11. Reproduce the problem with the Object Browser panel.
12. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.
13. Save the panel's contents to an HTML file and send the file directly to our support team.