Normal
The real issue is not that the plugin is slow. The keyboard hook timeout is long enough to process the lookup, this has been discussed many times.What actually happens is that when Windows is low on resources, it starts to page data, which occurs in thrashing. Even if the plugin processes each message in few milliseconds, the thrashing can cause mediaportal to stop responding for few seconds. If that happens, windows decides to stop posting messages (without even knowing that windows' paging mechanism itself caused the slow response).If you want to read little bit more about this, check winapi - Did MS change something about keyboard hooks in Windows Vista or 7? - Stack Overflow and the top answer.
The real issue is not that the plugin is slow. The keyboard hook timeout is long enough to process the lookup, this has been discussed many times.
What actually happens is that when Windows is low on resources, it starts to page data, which occurs in thrashing. Even if the plugin processes each message in few milliseconds, the thrashing can cause mediaportal to stop responding for few seconds. If that happens, windows decides to stop posting messages (without even knowing that windows' paging mechanism itself caused the slow response).
If you want to read little bit more about this, check winapi - Did MS change something about keyboard hooks in Windows Vista or 7? - Stack Overflow and the top answer.
