I just wanted to investigate the FamiTracker issue I reported in
So I did a big mistake and opened WinSpy and FamiTracker at the same time.
Immediately the system began to crawl to death logging stuff like:
(../../win32ss/user/ntuser/painting.c:1547) err: EP: Another thread invalidated this window
(../../win32ss/user/ntuser/message.c:790) err: Message WM_PAINT count 1 Internal Paint Set? FALSE
(../../win32ss/user/ntuser/msgqueue.c:1271) err: MsqSendMessage timed out 2 Status 102
Until here this is very good reproducible (the massive slowdown and the related spam)
Did not try to reproduce yet what comes next:
I tried to continue anyway and clicked in WinSpy the tab sheet "process" and the button "more" when it BSODed in Win32K again.
Our 0.4.7RC1 is massively plagued by Win32K BSOD stuff.
It is miles away from the stability level we had with the very good release 0.4.3 for example.
CORE-13931 FamiTracker 0.4.6 from rapps has invisible about-dlg