A bug in a Windows dll, that I managed to (on rare occasions) reproduce on an old laptop. It was not a recent development -- or at least, the code calling the Windows API was not new. I don't know if the Windows code changed recently.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
