Posted: 18 Feb 2021 10:24 EST Last activity: 18 Feb 2021 11:31 EST
Automating Internet Explorer: window handle leak
We have some RPA automations which access Internet Explorer failing with this exception:
"The current process has used all of its system allowance of handles for Window Manager objects"
When this occurs, the runtime also crashes but is unable to shut down. So the whole thing hangs until someone restarts the RPA machine. I believe this is happening because the automation often fails to shut down Internet Explorer between automations, even though there is specific code in the automation to stop Internet Explorer.
Runtime version: 8.0.2054.0
Windows OS: Windows Server 2012 R2 Datacenter
Internet Explorer: 11.0.9600.19940
I would like to upgrade the runtime, but our Pega is version 8 and it will be nearly a year before we can upgrade given business priorities. We are in the process of updating the runtime to the most recent 8 SP1, but have to get through a bunch of required approvals first.
Any idea on how to mitigate or eliminate this issue?
@StephanieG8434 If this is an issue that has already been addressed in the product, then an upgrade would resolve it. You'd need to work with support to determine if this is an issue we've already addressed. For the time being, you might consider adding logic to kill the IE process if upgrading a more recent version is not an option. This might work. You can do this by calling the Process.Kill() method. You could do this in a script relatively easily. Here is a series of scripts we use. You can call the first one and it uses the second two methods.
public bool KillProcess(string process, int waitMsToExit)
bool isProcessKilled = true;