Is it test complete itself cause tested application to crash?
Hi,
Randomly i get tested application crashed at installation stage during our automation - "The xxx.exe process crashed.". However, we never run into such process crash situation during manual installation.
Once a time i got one error message in system event log when it said my tested application process crashed:
Error 15/03/2016 4:54:14 PM 1000 Application Error
Faulting application name: WriteProfessionalEditionsTDPTrialKey.exe, version: 1.0.0.0, time stamp: 0x56e7aaae
Faulting module name: tcMSAAAppHook.dll_unloaded, version: 0.0.0.0, time stamp: 0x5473624c
Exception code: 0xc0000005
Fault offset: 0x000000001da0dcb7
Faulting process id: 0xc30
Faulting application start time: 0x01d17e9837f39073
Faulting application path: C:\ProgramData\Package Cache\BC6A34D9BBA18EC97E537E4D92B69706818C8E71\WriteProfessionalEditionsTDPTrialKey.exe
Faulting module path: tcMSAAAppHook.dll
Report Id: 7da35591-ea8b-11e5-acfc-0050562dafaf
Apparently the faulting module tcMSAAAppHook.dll is one from TestCompelete, and it caused my test application to fail.
In most other cases i can't get any error info from system event logs when it says my tested application process crashed. I think it's likely that test complete is injecting something into the tested application which cause the application to fail.
I have to rerun tests everytime i get "The xxx.exe process crashed" at installation stage in automation, which is quite frustrating. Are there any settings that will NOT allow to inject extra assemblies into tested application?
And i'm not sure whether it's really an issue in our application, or it's an issue relates to TestComplete.
Thanks,
Ocean
