Forum Discussion

SuperTester's avatar
SuperTester
Contributor
5 years ago
Solved

dllhost.exe crashing

Hello,

I have been encountering an issue where my dllhost.exe will crash during test playback. I have been getting help from Tech Support for a few weeks on this and its still an issue. I'm wondering if anyone has encountered this issue, or maybe there is a really simple solution that we're overlooking.

The dllhost.exe will crash during test play back when TC opens Acrobat DC or another program called Excel Compare. Essentially, the crash will occur when TC is accessing other software during test playback. Now the crash is not catastrophic, playback with continue performing playback. Interestingly, When Acrobat crashes, it will be logged in the windows event log and a adobe module will be identified as the faulting module. However, when Excel Compare (the other software tool being used) crashes, it will not be logged in Windows events. I contacted Adobe Acrobat and they maintain that nothing is wrong on their end. Note that either Acrobat crashes, or Excel compare, but never both during test playback.

Unfortunately, I cannot replicate the crash while using SmartBear's Report Generator Tool.

One idea is to reproduce the issue by involving another application that uses hooks and loads them into other processes when running. Essentially, see if I can recreate the crash using software that works similar to Test Complete. Apparently, Spy++ in message trace mode behaves in this manner. However, I have found any useful documentation to help guide me through the process.

  • Hi SuperTester,

     

    I think the issue you faced is very specific, and it depends on your environment. I'm glad to hear that you are already working with the Support Team as this question requires a deep investigation.

1 Reply

  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)

    Hi SuperTester,

     

    I think the issue you faced is very specific, and it depends on your environment. I'm glad to hear that you are already working with the Support Team as this question requires a deep investigation.