The information in this article applies to:
SYMPTOMSWhen a print job is terminated, the amount of available memory reported in the Program Manager's About box declines. This indicates that allocated memory objects remain on the global heap. CAUSEOne possible cause is an application that calls the print job abort procedure directly through its instance thunk. If, after this call, the print job is aborted and the application exits its printing loop without calling the ABORTDOC printer escape, the print job will not be properly aborted and allocated memory will be left on the heap. RESOLUTIONThe abort procedure returns FALSE if the print job has been aborted. If the abort procedure returns FALSE, the application should call the ABORTDOC printer escape in Windows 3.0 or AbortDoc() in Windows 3.1. The following code fragment demonstrates this procedure:
STATUS
MORE INFORMATION
An application registers its printing abort procedure with Windows by
calling the SETABORTPROC escape in Windows 3.0 or SetAbortProc() in Windows 3.1. Windows automatically calls the abort procedure during the NEWFRAME or NEXTBAND escape. If the print job is aborted during the NEWFRAME or EXTBAND escape, Windows automatically calls the ABORTDOC escape/AbortDoc().
Additional query words: 3.00 3.10
Keywords : kb16bitonly kbDSupport kbSDKWin16 |
Last Reviewed: July 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |