The functional complaint is that fingerprint login becomes non-responsive and password login becomes iffy in collecting password input because of the CPU load.
This CPU load suggests a bug of a loop that also allocates but then fails to relase memory - a memory leak. If the DP Service is cycled via Windows Computer Management->Services, the program re-starts at 14MB - a 2 orders of magnitude diff in memory consumption and much more believable for its purpose. I have seen it go as high as 11GB in the above scenario. In this case, the memory consumption fell over many minutes to settle at 1.1GB, again a questionably large consumption for the presumptive role. DigitalPersona ist eine Suite von Sicherheitsanwendungen fr groe Unternehmens- und Unternehmensnetzwerke.
Attached a screen shot showing 9.6GB of consumption. Die Original DPAgent.exe Datei gehrt zur DigitalPersona Software von CrossMatch. If the Task Manager is brought up immediately, "DigitalPersona Local Host" shows in the Processes tab with memory consumption that makes no sense for its presumptive role. The system load and fan then calm down over a few minutes. Password login succeeds only with carefull patient typing needed with a heavily loaded system. If my computer is left running and most importantly locked for some time, typically > 60 minutes, then upon return the fan is running hard, the fingerprint login is non-responsive, and the cursor on the login screen exhibits flicker-in-place typical of a pinned CPU situation.