🚀 go-pugleaf

Hi Remy,

Sorry, for the un-clear code, as mentioned the problem occur on the free-ed 
dll code, and
memory/code area belong  some routine which I do not know, bcoz the 
debugger's stack
only show the ntdll or vclbpl.  That reason I could not show you the code 
where the error
start from.

Beside, the problem on occur with this DLL, which had DsPack (DirectShow, 
DirectX),
it did not occur on other DLLs.

Basically, I had 2 PCs, both also running the same program -  Host and DLL.
1 PC run as Server and the other as Client, like remote control system.

The client will automatically launch the DLL after server had manually 
launch the DLL
(again via TWSocket), it will LoadLibrary and the call PluginInit to create 
the FORM.

FYI, the closing problem only occur on client PC not the server PC.

How it was closed?

When server DLL's close by clicking the 'X' or press Alt-F4, it will send 
MDC_EXIT to
the client PC, on received MDC_EXIT the client PC will call PostMessage 
WM_CLOSE
and it was trigger from the timer event - ProcessQue.

During the closing process, it will inform the Host by PGII_PLUGINFREE and 
give the
estimate time period to free the close FORM. After cleaning up all the 
things it again
inform host by PGII_PLUGINCLOSED, it ready to be free/unload.

From the host program, it used timer to check for unload the DLL, before it 
really free
the DLL, it call PluginExit to double confirm, otherwise it force to free 
the FORM.
as the code given.

So, I was sure that the PluginExit will not be call during the FORM closing 
process.

Beside, if the client PC do not run as broadcaster, ie access the DsPack 
components
load Mpeg file for streaming video and audio to server, the problem of 
closing never
occur.

Hope this could help you to understand to my problem.

Question, usually take how long for a DLL with form to do complete cleanup?
How can I send the actual code to your private email (only the DLL) .

Regards
KL Chin


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:41c7e9f2@newsgroups.borland.com...
>
> "KL Chin" <klchin@1asia.com.my> wrote in message
> news:41c7b41a@newsgroups.borland.com...
>
>> Sorry, I will not able to show the complete code, it was too big.
>
> I don't want the complete code.  Only the parts that are relavant to this
> discussion - the code involved in shutting down the DLL and application.
>
>> BTW, not I wanted to access the DLL after it is freed. It was some
>> how called during the unload/closing process and it was always had
>> problem when Server issue a close command.
>
> Then your shutdown code is faulty.  That is why I asked you to show it.
>
>>                               PostMessage( Handle,WM_CLOSE,0,0 );
>>                               PostMessage( Handle,WM_DESTROY,0,0 );
>
> Do not destroy the Handle.  TForm will do that for you automatically when
> appropriate.
>
>> __declspec(dllexport) int WINAPI PluginExit( void )
>
> When does the application call this?
>
>>     if ( frMxCast )
>
> Are you guaranteeing that the application never calls PluginExit() while 
> the
> form is in the process of closing itself?  If not, then you may have a
> potential timing issue where frMxCast is not NULL yet but the form and
> PluginExit() are both going to try to free the same memory multiple times.
>
>> __declspec(dllexport) int WINAPI PluginInit( HWND hWnd,  viPluginInTInfo
>> lpInTInfo )
>
> When does the application call this?
>
> Nothing in the code you have shown indicates where the actual error is
> occuring.  But then, you did not show any of your application code at all,
> either.  It is not very helpful to show the DLL code without showing the
> application code that is calling the DLL code.
>
>
> Gambit
>
>