Object Spy locks on application crash?

Thanks for the info Helen. Does the AUT have to be run in debug mode for this to happen? As it currently just causes TC to freeze. (It's not just the object spy .... it's the entire application)

I don't want to stop the entire run at this point.

I should explain ....

I run using my own framework. Which also uses it's own logging system. I don't use the built in logs at all.

My tests are all keyword & data driven via user populated spreadsheets. Each spreadsheet constitutes a "test pack".

When the application crashes, I need to extract any relevant information from the crash Dialog (which I do .... it's not a WerFault one). Log it (using my own logs). Kill the application. Abandon the current test pack. Then move onto the next one. All test packs for this application expect to start with a blank slate (for consistency) so killing everything at process level before I abandon is fine.

I was going to look at running in debug mode next, but if killing it at process level does the job (it does) then I'm fine with that. I already have a routine to terminate all it's processes (there are quite a few) as this has to be done before a DB restore (which all test packs do at the start as well) anyway.

According to the devs, the crash I'm causing is an unusual ones. Most application errors are not handled by WerFault, they are dealt with using internal mechanisms. But the one I'm hitting is due to a 3rd party DLL we use, which does drop into WerFault. So in most cases, I won't have to worry about it. The internally generated Dialogs are handled no problem.