Running the Components E2E tests locally show that the headless chrome instances that are started are not correctly recycled and accumulate quickly to take 100% of the CPU making them get slower and slower. This could also explain some timeouts on Helix. From VS I can only see a max of 2 tests running concurrently and here is a view of the chrome processes: