Forum Discussion
Do you have a particular pattern to the non-responsiveness? Does it happen at the same place or within similar functional processes? If so, you should be able to build into your code some sort of "Wait" methodology that, when attempting to execute the specific process, check to see if the application is responsive... if not, call Sys.Process(<application name>).Terminate().
- tristaanogre8 years agoEsteemed Contributor
Just remembered... there's another solution.
https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/properties/freeze-diagnostics.htmlTake a look at that option and see if it works for you.
- krkarthik_info8 years agoFrequent Contributor
Hi Robert,
Thanks for the suggestion on using Freeze Diagnostics.
It helped me to solve my scenario. On properties I have set process filter for my application and used application hanging timeout property. On using this, it terminates the application if not responding for given timeout and posts the dump file to the log and proceeds with the next test items.
Thanks
- krkarthik_info8 years agoFrequent Contributor
Hi,
Thanks for the reply.
I don't have a specific pattern where the application goes to non-responsive mode. Randomly goes into the non-responsive during execution of different test items.
As you suggested, I will have a look into the Freeze diagnostics options and see whether it helps me out.
Thanks,
Karthik K R
Related Content
- 6 years ago
- 2 years ago
- 13 years ago
Recent Discussions
- 5 hours ago