Re: Process not always exiting
- From: "Joe" <joe@xxxxxxxxxx>
- Date: Tue, 13 Dec 2005 14:19:24 -0800
Look for code executed from DllMain() that could use some other .dll --
except kernel32.dll.
Code executed from DllMain() that uses code from any .dll except
kernel32.dll can cause a hang on unload.
"Mark Hampton" <mhampton.removeme@xxxxxxxxxxxxxxxxxxx> wrote in message
news:ubseUiBAGHA.216@xxxxxxxxxxxxxxxxxxxxxxx
> Not sure if this is the appropriate forum, but it seems like it is.
>
> We have an application that does not always exit when the user closes it
> (all windows are closed, but it hasn't unloaded DLLs yet). Since this is a
> 4GL application (PowerBuilder), we have no control really over the way the
> program exits; Additionally, we use various external DLL's for various
other
> work (sockets, some DLLs written by other companies, etc).
>
> So, the question is, what can prevent an application from exiting in the
> Win32 world? Threads waiting on sockets? Threads waiting on a mutex?
>
> Any kind of pointers would be useful; If needed, I can provide a list of
> open objects dumped from Process Explorer.
>
> Additionally, if anyone thinks I should open a support case, I'm willing
to
> try that, just give me pointers on how I should word the request so that
it
> gets to the proper group.
>
> Thanks.
>
>
.
- References:
- Process not always exiting
- From: Mark Hampton
- Process not always exiting
- Prev by Date: Re: Process not always exiting
- Next by Date: Re: Synchronous Read/Write
- Previous by thread: Re: Process not always exiting
- Next by thread: Re: Process not always exiting
- Index(es):
Relevant Pages
|