Re: Memoryleak in SSL.Connection
Andre Reitz <[email protected]>
| Newsgroups | gmane.comp.python.cryptography |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 8 Apr 2004 09:07:24 +0800 Ng Pheng Siong <[email protected]> wrote: > On Thu, Apr 01, 2004 at 09:49:07PM +0200, Andre Reitz wrote: > > here is my patch, which should work in any case: > > (but not so efficient) > > Is it easy to induce/observe the leak? > > I think one possible cheap way to fix the cyclical references is to do this > > self._write_bio = None > self._write_nbio = None > self._read_bio = None > self._read_nbio = None > > at a strategic spot, perhaps in close(). This gets rid of the mode test at > every invocation of read/write/send/recv. > > What do you think? > not really a good idea. this would work for myself, but perheps if a thread exits with an exception and doesnt call close... there would be the same problem.... Greetings Andre' > -- > Ng Pheng Siong <[email protected]> > > http://firewall.rulemaker.net -+- Firewall Change Management & Version Control > http://sandbox.rulemaker.net/ngps -+- Open Source Python Crypto & SSL -- __________________________________________________________________________ Als Technologieunternehmen konzipieren und entwickeln wir maßgeschneiderte Feedback- und Monitoring-Systeme - wie beispielsweise Lösungen für Beschwerde- und Ideenmanagement. Mit dem Inquery® Survey Server bieten wir eine der leistungsfähigsten Standardlösungen für Online-Umfragen mit dem Schwerpunkt auf der Messung von Kundenzufriedenheit an. __________________________________________________________________________ Inworks GmbH Andre Reitz, Leiter Entwicklung Hörvelsinger Weg 39, 89081 Ulm, Germany Tel +49 (0) 731 / 93807-21 Fax +49(0)731/93807-18 Internet: http://www.inworks.de