Re: [pyOpenSSL] memory leak?

[Martin <md...@md...>]

tis 2003-01-14 klockan 14.44 skrev Zoltan Felleg:
> i,ve tested the CVS version, it works greatly for me (does not leak)=20
> even when the verify callback function is a class method.

Great, so the cyclic stuff seems to be working!

> just a bit of another thing: i've fixed my real server, which served the=20
> clients in a loop of select/recv pairs, where only the first client was=20
> served at any one time even if the select call returned more than one=20
> readable sockets. the first client was always the server's socket on=20
> which it accepted new connections, so basically a test, which was a=20
> thousand clients connecting and then disconnecting, took the following=20
> order: a thousand client was connected, and just after that, when no new=20
> clients were connecting, were the clients disconnected from the server=20
> side. (if it is unclear, please let me know, i'll try to express myself=20
> more clearly). i do know, that this method (ie. not recv-ing from all=20
> the sockets the select returned is a BAD THING), and i will not return=20
> to that method again, but the clear text version of the server (without=20
> openssl) had no leak even in that case, while the openssl version did=20
> have leakage. if this information is useless, please disregard it.=20
> thanks for the help so far,

Er. I don't think I understand you. Are there still versions of your
program that leak, even with the CVS version of pyopenssl? I wouldn't be
surprised, as I'm definitely not sure if I manage to free all the memory
allocated by openssl (the non-existant documentation is very vague on
reference counting and allocation).

Please explain, ideally with a minimal program that still leaks. ;)


/Martin