a thread in symcscan.exe spin-locks and holds one core in case that SPE service is started upon OS boot time
Last Updated May 01, 2017
An issue is reported that a thread in symcscan.exe spin-locks in case that service is started upon OS boot time. That is, if system is equipped with 4 CPUs, then symcscan.exe consumes about 25% of system CPU time.
As seen in the above, symcscan.exe is calling Windows API StartServiceCtrlDispatcher() as per design of Windows Service. And StartServiceCtrlDispatcher() is not able to return, which causes hang-up state of symcscan.exe.
This issue has been reported in an environment where attached NIC is being disabled.
This issue occurs only on the virtual environment.
no error message is yielded.
This issue has been resolved in SPE 7.5.5 under etrack #3915419.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe