Forum Discussion

twhitehouse's avatar
twhitehouse
Contributor
10 years ago

'Process "ieexplore" stayed in the system after the close command was used."

At seemingly random times in my script, Internet Explorer will remain opened.   I also have a loop to loop through all browsers on the system.  In this loop, 2 internet explorer processes are actuall...
  • k_de_boer03's avatar
    k_de_boer03
    10 years ago

    I use this code to close internet explorer (Jscript):

     

    while(Sys.WaitProcess("iexplore").Exists){
        Sys.Process("iexplore").Close();
}

    It may take a few loops before it actually closes, but I consider it a cleaner more stable way than to abruptly kill the process with Terminate().

twhitehouse's avatar
twhitehouse
Contributor

This would be a nice catch all if IE was being stubborn, which it might be...lol.  Thanks!

Colin_McCrae's avatar
Colin_McCrae
Community Hero
10 years ago

The drawback I can see with k_de_boer03's approach is that it could get stuck in an eternal loop if IE resolutely refused to close. I really try and avoid anything in a test which can result in an endless loop. Especially in large, long running test suites.

 

Something like that, I would have a secondary exit clause in the loop. Either time, number of attempts, or both. If it exited due to the secondary clause, then I would attempt to kill the process. If that also failed, I would then stop the test.

  • twhitehouse's avatar
    twhitehouse
    Contributor
    10 years ago

    That is a good point.  I did not think about getting stuck in an infinite loop.  I guess I would have found out the hard way...lol.

     

    The secondary exit is a good solution to accompany the first solution though.  Looks like there are a few ways to approach this.  Thanks again.

  • k_de_boer03's avatar
    k_de_boer03
    Contributor
    10 years ago

    I had used the Terminate() solution before, and hasitated to use this code for a while for the exact same reason that I was afraid that it would slow down my test suite, or possibly never end. But so far so good, never had any infite loops.

     

    Maybe my test suite gained a few seconds, but I prefer this solution because when you open the browser after Terminate(), you'd often get a message like "The browser has been closed unexpectedly, would you like to restore?" or something like that, I didn't want that.

     

    And besides, if a process refuses to close infinitely, then I blame the process, not the code :)

    • twhitehouse's avatar
      twhitehouse
      Contributor
      10 years ago

      I would not have thought of that.  Thanks for sharing the reasoning.  This has been a helpful thread...thanks.