Forum Discussion
chrisb
11 years agoRegular Contributor
I had the same problem. I believe the issue was caused by trying to close a process that was no longer running. Resolved this problem for good by increasing the delay before checking to see if the process still running and also adding some code to break out of the loop if IE was determined to no longer be running:
function TerminateIEProcesses() {
var process, i;
for (i = 0; i < 20; i++) {
process = Sys.WaitProcess("iexplore", 2000);
if (!process.Exists) {
break;
}
process.Terminate();
aqUtils.Delay(1500);
}
}
function TerminateIEProcesses() {
var process, i;
for (i = 0; i < 20; i++) {
process = Sys.WaitProcess("iexplore", 2000);
if (!process.Exists) {
break;
}
process.Terminate();
aqUtils.Delay(1500);
}
}
Related Content
Recent Discussions
- 3 days ago