Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!know!newmedia!jim
From: jim@newmedia.UUCP (Jim Beveridge)
Newsgroups: comp.windows.ms.programmer
Subject: DLL Memory handling
Keywords: WEP, GlobalAlloc
Message-ID: <433@newmedia.UUCP>
Date: 24 Jan 91 16:52:46 GMT
Organization: New Media Graphics, Billerica, MA
Lines: 20

The WEP (windows exit procedure) for my DLL tries to free the 
global memory that it had allocated over the course of time.  
Unfortunately, the moment I try and deference the first element
in the linked list, the entire system hangs.

If the DLL is explicitly loaded, the WEP works properly.  
If the DLL was implicitly loaded, all global memory appears 
to be freed _before_ the WEP is called.  This is a problem, 
because I need some information out of global memory to 
properly shut down the DLL.

How can I work around this problem?

(One suggestion has been to use a local heap instead of 
the global one.)

	Thanks, Jim

--
"If I wanted a .sig, I would have written one."