The process is not killed after the test
Hello, Since we installed the new version of TestComplete (version 8.50.618.7), we have a problem. If I run my application from TestComplete, the process is not kill after closing my a...
Forum Discussion
Dmitry_Nikolaev
Staff
StaffHi Christophe,
Is it possible for you to send us your application so we can reproduce and investigate the problem here? If you cannot send us the application, please follow the steps below:
1. Download the Debugging Tools for Windows x86 package from:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi
and install it.
2. When the tested application is closed, make sure that the process is still running, open the "Start | Run..." dialog and execute the following command:
"C:\Program Files\Debugging Tools for Windows\windbg.exe" -pn MyApp.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"
This command will make WinDbg write a memory dump of the tested application 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. Send us all of the generated dump files via the Contact Support form.
Is it possible for you to send us your application so we can reproduce and investigate the problem here? If you cannot send us the application, please follow the steps below:
1. Download the Debugging Tools for Windows x86 package from:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi
and install it.
2. When the tested application is closed, make sure that the process is still running, open the "Start | Run..." dialog and execute the following command:
"C:\Program Files\Debugging Tools for Windows\windbg.exe" -pn MyApp.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"
This command will make WinDbg write a memory dump of the tested application 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. Send us all of the generated dump files via the Contact Support form.