4 ms·
Great Post! You would think that unlocking the screen would be highest priority task for a general purpose OS after it has woken up from sleep, but surprising
by justforfunhere 6y ago
Great Post!
You would think that unlocking the screen would be highest priority task for a general purpose OS after it has woken up from sleep, but surprising to see that other processes manage to outrank it.
Whats interesting to me is that this LockApp.exe was waiting to get the CPU for a full 19 seconds after it was ready. 19 seconds should be an eternity, I guess.
Since the screen was locked and LogonUI.exe had not got the chance to run yet, what other processes were holding on to CPU at that time. Any ideas on that?
- tambre 6y ago>Any ideas on that? As he explains, processes with a GUI trying really hard to render despite it not being possible, as the screen hasn't been unlocked yet. Presumably another Windows bug. Also hardware drivers initializing stuff. Including spinning for an eternity – his mouse and keyboard driver apparently spinned for 700ms.