Starting the service leads to full CPU usage on one thread (CPU core).
That is, on a 4 core machine, process will consume 25% steadily once started.
It seems the process is some sort of constant loop.
Our setup:
- There are two servers (both Windows Server 2022 21H2)
- One is the Master, other is a farm member
- Issue happens on both servers. Just starting the service, it will full CPU moments after.
By now, we have disabled the service, but the statistics provided are very useful for us - we would be glad if it were possible to re-enable it.