🚀 go-pugleaf

"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