Forum Discussion

mkirkland's avatar
mkirkland
Contributor
13 years ago

Load test locks up IE on certain actions

I am having a problem when recording the http load test in TestComplete. I can record test that are moving across various pages but the issue i am having is that my we application interacts with some scanner and printer hardware. When in try to scan through the application test complete locks up IE and i have choice but to kill the IE process. I have verified that all these same processes work with no issues when load testing is not used, i have tried it with and without https/http with and without anitivirus enabled.



Not really sure where to go from here with the lockup issues. My application works only with IE so moving browsers is not a choice. I have upgraded to the latest version of TestComplete with no resolve. Help would be greatly appreciated.

3 Replies

Sort By
  • Abramova's avatar
    Abramova
    Staff
    13 years ago

    Hi Matt,


    To help us investigate the issue, please send us your application via the Contact Support form.


    Also, please generate the dumps for both TestComplete and Internet Explorer and attach them to your message. To generate the dumps, please follow the steps below:


    1. Download the Debugging Tools for Windows package from:

    http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi

    and install it.


    2. When the issue occurs, open the "Start | Run..." dialog and execute the following command:

    "C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe" -pn TestComplete.exe -Q -pd -c ".dump /m C:\TCDump1.dmp;q"


    This command will make WinDbg write a memory dump of the TestComplete.exe process to the "C:\TCDump1.dmp" dump file. After the dump is written, WinDbg will be closed.


    3. In the same way, generate a dump for the Internet Explorer process:

    "C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe" -pn iexplore.exe -Q -pd -c ".dump /m C:\IEDump1.dmp;q"


    4. Wait for two minutes.


    5. Repeat steps 2-4 twice more (but correct the dump file names in the command lines).


    6. Attach all the generated dump files to your message.