SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 2 of 2

Thread: ie4_trap.dll

  1. #1
    Junior Member
    Join Date
    Apr 2008
    Location
    New York
    Posts
    11
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    ie4_trap.dll

    We are using WinRunner 9.2 with scripts stored in Quality Center 9.2. We have been having a problem with scripts failing after two or more hours with an Explorer crash. In trouble-shooting, we found several instances in our framework where Explorer is stopped and started. We eliminated all (I think) of them.

    Now my script failed after 13 hours, 47 minutes with an Internet Explorer crash in ie4_trap.dll on one machine (with the debugger running), after 5 hours, 49 minutes on another (with IE crash notice), and 2 hours, 21 minutes (with IE crash notice) on the third. My script is a fairly tight loop that takes about 1 minute each iteration to launch my application, logon to a data server, then logoff and close the application. The crash occurs after the launch and before the logon. It occurs even when the logon and logoff are eliminated from the script.

    As far as I know, there is no call to Internet Explorer. (The next several hours will be devoted to reading through the framework again looking for IE calls.) However, since we are attached to Quality Center, do you know whether and how WinRunner is using the ie4_trap.dll?

    Any ideas for further investigation?

    It is imperative that we automate overnight testing and this problem is preventing unattended testing.

    Thanks for any assistance.

  2. #2
    SQA Knight
    Join Date
    Jun 2002
    Location
    Cupertino, CA, USA
    Posts
    2,164
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: ie4_trap.dll

    Try running without the WinRunner WebTest addin loaded - that will tell you if it's a WinRunner or QC issue. Almost guranteed it's a WR issue - there are known memory leaks, and long tests usually fail with similar issues. It's a good practice to keep tests fairly short (< 30 min), and run them in a suite (especiall if you have QC). If you're running a longevity test, you may be better off using LoadRunner, or a similar tool which implements HTTP requests directly (instead of through the Browser).

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 11.54%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:27 AM.

Copyright BetaSoft Inc.