Unexpected amount of chrome.exe process

  • KM03603120
  • 26-Feb-2020
  • 26-Mar-2020


Chrome browser opens a lot of background processes.


The reason why chrome do this is because of the following:
HTML/ASP text on the page
The plugin you have loaded
The app you have loaded
Frame (i.e. menu system on left)
For each option from the list above, Chrome opens a process in the background.
Chrome works like this to improve the user experience, so if one of these options crashes, for example, the web browser will keep working with no issues.
This setting helps the Chrome browser to run several plugins, in parallel and improve the user experience.
As an alternative, refer to https://support.microfocus.com/kb/kmdoc.php?id=KM03081389
In addition:
1. The unexpected amount of chrome.exe process, it’s not controlled by TruClient. Actually, it’s Chrome’s behavior. If you open Chrome (pure Google Chrome browser), even only open a blank page, there are several chrome.exe processes. As Chrome keeps improving its security, more chrome.exe processes are opened by newer version Chrome. Chrome uses multiple processes to improve its security, robustness, and user experience. Thus, every TruClient virtual user opens a dedicated Chrome instance, which contains several chrome.exe processes.
2. The chrome browser itself has a memory leak. To overcome the memory leak issue from the browser, TruClient has to monitor browser memory, restart the browser when the amount of memory leak is detected. But this monitoring and restarting mechanism are only enabled when “New User Simulation” is enabled. When it’s disabled, due to browser memory leak, more memory will be used as time goes on.
3. The memory leak is not caused by browser upgrade. Every version of Chrome has a memory leak, more or less. In general, the newer version browser tends to use more resources to improve user experience and security, which might cause it easier to detect more memory leak.
4. The side effort of the browser restart mentioned in #2 is, browser session information (such as some cookie, cache, and login information) will be lost. That’s why it’s not recommended to put login logic in Init and put logout logic in End. If so, when the browser gets restarted, login information is lost, but the login logic in Init will not be executed again. Then, steps in Action may fail. The recommended way is, put login logic, actions, and logout logic all in Action, and enable “New User Simulation”.