BUG: Screen Saver Not Getting WM_DESTROY in Windows NT
PSS ID Number: 140727
Article Last Modified on 5/7/2003
The information in this article applies to:
- Microsoft Win32 Application Programming Interface (API), when used with:
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
This article was previously published under Q140727
SYMPTOMS
When a 32-bit screen saver running under Windows NT 3.5 or 3.51 terminates
due to a mouse move, mouse click, or key press, although the application
terminates, the window never gets the WM_DESTROY message. Failure to
receive this message poses a problem as applications are not able to call
clean-up routines such as deleting GDI objects, freeing memory objects, and
so on. This results in a memory leak and further reduction of system
resources each time the screen saver application is run.
This problem does not occur when the screen saver is run in Test mode under
Windows NT's Control Panel. In Test mode, the screen saver receives the
WM_DESTROY message.
STATUS
Microsoft has confirmed this to be a problem with the Scrnsave.lib file
that shipped with the Win32 SDK for Windows NT 3.51 and Windows 95. It is
scheduled to be fixed in the next release of the Win32 SDK. However, this
problem is specific to Windows NT; it does not occur with 32-bit screen
savers under Windows 95.
Additional query words: 3.50
Keywords: KB140727
Technology: kbAudDeveloper kbWin32API kbWin32sSearch kbWinNT350search kbWinNT351search kbWinNTS350 kbWinNTS350search kbWinNTS351 kbWinNTS351search kbWinNTsearch kbWinNTSsearch kbWinNTW350 kbWinNTW350search kbWinNTW351 kbWinNTW351search kbWinNTWsearch