At some point, the Whatpulse client stops tracking keys but has no problems with mouse clicks. I have to reopen the client to make it work again.
This often (but not always) happens when CPU usage is very high (100 % for several seconds). Thus, the problem is very similar to here.
- Client runs with Admin rights
- I looked into app.log or app.old.log, respectively. No clue to this, other than most of the lines are spammed with a “GetModuleFileNameEx failed” message. This also occurs on days where the client has no problems tracking all the keys, thus it probably won’t be the reason
- Win10 64-bit. If more system data might be of interest, I will provide them of course as well
How can I fix this problem? It really annoys me and screws up the whole idea of this app.