🚀 go-pugleaf

Because the ServerSocket1->Socket->Connections[0]->SendStream(SendPms); deletes
the stream for you. This is from the BCB component help file description :-
-------------------------------------------------
TCustomWinSocket::SendStream
bool __fastcall SendStream(Classes::TStream* AStream);

Use SendStream to write to the socket connection. SendStream may write from a
socket that is expected to write to the connection without a notification to
signal the connection's readiness to read. SendStream reads information from the
stream indicated by AStream and writes it to the socket connection. The value
returned by SendStream indicates whether any information was successfully
written to the connection.

Note: The Stream passed as a parameter to SendStream becomes "owned" by the
windows socket object.  The Windows socket object frees the stream when it is
finished with it.  Do not attempt to free the stream after it has been passed as
a parameter.
-------------------------------------------------
The salient point is, "The Windows socket object frees the stream when it is
finished with it.  Do not attempt to free the stream after it has been passed as
a parameter." So, take out the delete line - there will be no memory leak.
-- 
Mark Jacobs

"Byanex" <chikui@bol.com.br> wrote in message
news:41586e5b$1@newsgroups.borland.com...
| One more thing, the server code below presents some acces violation errors
code when run with "delete" line, any one know why???
| void __fastcall TForm1::Button1Click(TObject *Sender)
| {
|     TMemoryStream* SendPms = new TMemoryStream();
|     Image1->Picture->Bitmap->SaveToStream(SendPms);
|     SendPms->Position=0;
|     ServerSocket1->Socket->Connections[0]->SendStream(SendPms);
|     delete SendPms; // <<-- This line
| }
|
| Without the delete line the code runs fine, any problem if just take out this
line???