Article View: comp.windows.ms
Article #13442Mem eating
From: Parker Waechter
Date: Thu, 12 Jan 1989 04:25
Date: Thu, 12 Jan 1989 04:25
16 lines
1111 bytes
1111 bytes
An aplication I am writing seems to be holding 20K or so after the program terminates (as checked by command window aboutbox). I was careful about dealocating my pens and brushes, and the big blocks of memory are done with their LocalAlloc and GlobalAlloc (I do have a 9 byte block allocated in declaration ie BYTE x[9]). I call free's in my WM_DESTROY. Has anyone had a similar problem with their programs that could point me to something else to check? PS what is the difference between Local/GlobalFree and Local/GlobalDiscard? The man page for both says it returns memory to the heap, so what's the difference? ------------------ parker@sun.com No these are only my problems, opinions, questions...not anyone elses.
Technical Details
Message-ID:
<33587@grapevine.uucp>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sun!grapevine!parkerShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sun!grapevine!parker From: parker@grapevine.uucp (Parker Waechter) Newsgroups: comp.windows.ms Subject: Mem eating Keywords: disgard free memory Message-ID: <33587@grapevine.uucp> Date: 12 Jan 89 04:25:28 GMT Organization: Sun Microsystems, Inc. - Mtn View, CA Lines: 16