I also used process explorer.
In process explorer I see the handle count increasing, but the handle
itself is not added
to the list of handles.
Kind regards,
Nicolas.
-----Original Message-----
From: owner-xmlblaster at server.xmlBlaster.org
[mailto:owner-xmlblaster at server.xmlBlaster.org]On Behalf Of Marcel Ruff
Sent: donderdag 28 oktober 2004 16:01
To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] c++ client handle leak ?
Quartier, Nicolas wrote:
> Hi,
>
> I'm writing a c++ client using XB library 0.91 on win 2000.
> The client connects to the server using sockets.
> Does anyone know of a handle leak in the client?
> Because everytime the client pings the server,
> the number of handles of my client program is increased with 4.
> The memory usage and the number of threads are stable though.
>
> Maybe I'm something wrong ?
File descriptor handles or socket specific handles?
How do you measure the consumed handles?
thanks
Marcel
>
>
> Thanks and kind regards,
> Nicolas.
> - - - - - - - DISCLAIMER - - - - - - - -
> Unless indicated otherwise, the information contained in this message is
> privileged and confidential, and is intended only for the use of the
> addressee(s) named above and others who have been specifically
> authorized to receive it. If you are not the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> message and/or attachments is strictly prohibited. The company accepts
> no liability for any damage caused by any virus transmitted by this
> email. Furthermore, the company does not warrant a proper and complete
> transmission of this information, nor does it accept liability for any
> delays. If you have received this message in error, please contact the
> sender and delete the message. Thank you.
>
--
http://www.xmlBlaster.org
- - - - - - - DISCLAIMER - - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically
authorized to receive it. If you are not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
message and/or attachments is strictly prohibited. The company accepts
no liability for any damage caused by any virus transmitted by this
email. Furthermore, the company does not warrant a proper and complete
transmission of this information, nor does it accept liability for any
delays. If you have received this message in error, please contact the
sender and delete the message. Thank you.