Internet Explorer Instances (iexplore/iexplore*32) (IE integration)

[AnastasiosKrap1]

Hello everyone, in a scenario with browser-based integration (i.e. IE), we noticed that even though we use the 'Terminate' stage after all actions have been completed, ONLY one instance of IE is killed. Specifically, on browser 'Launch' there are 2 new created instances: - iexplore.exe (IE main instance) - iexplore.exe *32 (IE tab instance) As it seems, the 'Terminate' stage will kill the first instance only (i.e. iexplore.exe) and the second will still there as a garbage. The result is that after long run, we will have memory exception as it will be full of IE instances. Why the 'Terminate' stage doesn't kill ALL the IE instances? How could we overcome such an issue? *Note that we thought of a solution that involves 'Kill Process' on the 'Clean Up' stage, but it is not the best practice.

[Deep.Shah]

Have you tried changing registry setting HKEY CURRENT USER\Software\Microsoft\Internet Explorer\Main to 0. This will ensure only one iexplore.exe process. You can find about this in Browser Automation Guide.

[Christer__Tellefsen]

We use Utility - Enviroment - Kill Process Input: Process Name - ""iexplore"" That kills both

[John__Carter]

Another option is to spy the IE window using Win32 mode and then use the Close action. Terminate is the same as 'end process' in Task Manager, and not every application like to be closed down this way.