I have recently discovered this also. I am not automating outlook.exe whatsoever. I do have a TC script running, checking if a (non-outlook) process has an "Exists" property of "True" or "False", then it delays for 1 second before checking again.
While this is running, if I switch to Outlook, it will often crash.
Using Splunk, I searched for [outlook.exe TaskCategory="Application Crashing Events"], which shows events from the system event log. Here is one such event that just happened (where Outlook crashed):
3/21/18
1:51:58.000 PM | 03/21/2018 01:51:58 PM LogName=Application SourceName=Application Error EventCode=1000 EventType=2 Type=Error ComputerName=<omitted> TaskCategory=Application Crashing Events OpCode=Info RecordNumber=13392 Keywords=Classic Message=Faulting application name: OUTLOOK.EXE, version: 16.0.8431.2215, time stamp: 0x5a745d5e Faulting module name: tcTextSpy.dll, version: 12.0.122.7, time stamp: 0x57990e78 Exception code: 0xc000000d Fault offset: 0x0003325c Faulting process id: 0x2d60 Faulting application start time: 0x01d3be0bccdb9687 Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE Faulting module path: c:\program files (x86)\smartbear\testcomplete 12\bin\extensions\tcTextSpy.dll Report Id: f5aa3c4a-33f2-46fc-87a6-3def8b3c3408 Faulting package full name: Faulting package-relative application ID: |
