smaglio81
commented
2 months ago As a follow-up on this, we decided to upgrade the servers to 2019 as the solution. So, I don't think I'll be able to validate any solutions to this issue.
Hopefully, you'll be able to reproduce and resolve the issue internally.
Hello,
CfT version: 126.0.6478.63
We're seeing a 100% CPU issue on Windows Server 2016 (Version 1607, OS Build 14393.7070).
When starting Chrome for Testing (both directly and through chromedriver), multiple instances of the chrome process will start and the CPU will climb to 100%. So far, we decided to only allow the issue to consume 100% CPU for ~2 minutes before closing we close the Chrome for Testing UI/Brower, but the belief is that the 100% CPU utilization would not stop if the process was not stopped. We have manually stopped the processes but using the Chrome UI to close the main window and all chrome sub-processes will then end soon afterwards (within a few seconds).
When opening Chrome for Testing directly (after closing the Chromium window pop-up on the first run), the CfT (Chromium) Task Manager shows that multiple processes for "subservices" are being started and those processes are consuming the CPU (Unzip Service, Data Decoder Service, etc).
Windows Server 2016 - Server1
Windows Server 2016 - Server2
Using the exact same application (copying/pasting the chrome/126.0.6478.63 folder from one system to another) we were able to reproduce the problem on Windows 2016 servers (seen above). The problem did not reproduce on other OS's:
So, it seems to be OS specific. Would you have any idea what might be different about the Windows Server 2016 OS which would cause this issue?
Windows Server 2019
Windows 10
Thanks in Advance