So, it crashes on launch? Is that what you're saying? If that's the case, then no, I'm not experiencing that problem.
Something you need to make sure of... IE sometimes tends to hang around in process memory after it has been closed. When you close a browser instance, you should make sure all copies of the process have been closed as well. I've experienced situations where, if I didn't do this, a number of strange problems would happen.
The following code is what I use to ensure this
function closeIEInstance() {
var counter = 0;
var browser;
browser = Sys.WaitBrowser('iexplore', 1000);
while((browser.Exists) && (counter < 60)){
counter++;
browser.Terminate();
browser = Sys.WaitBrowser('iexplore', 1000);
}
}
Robert Martin
[Hall of Fame]Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
