HTTPConnection::_on_headers seems to leak connection

已查看 28 次
跳至第一个未读帖子

Jefim

未读,
2010年5月24日 06:18:162010/5/24
收件人 Tornado Web Server
Hi,

The function HTTPConnection::_on_headers seems to leak connection if
exception is thrown.
This can lead to denial of service on the server.


David P. Novakovic

未读,
2010年5月24日 06:58:432010/5/24
收件人 python-...@googlegroups.com
Do you refer to the circular dependency between connection and request?

i'm fairly sure python can detect that these objects have reference to
them or not... no references is kept to the connection object... so if
the request object goes out of scope both of them will be garbage
collected..

I could be wrong though :)

D

Jefim

未读,
2010年5月24日 07:36:412010/5/24
收件人 Tornado Web Server
This does not mean memory leak, but the connection leak - the
connection is not closed

On May 24, 1:58 pm, "David P. Novakovic" <davidnovako...@gmail.com>
wrote:

Jefim

未读,
2010年5月24日 07:46:202010/5/24
收件人 Tornado Web Server
This does not mean memory leak, but the connection leak - the
connection is not closed

On May 24, 1:58 pm, "David P. Novakovic" <davidnovako...@gmail.com>
wrote:

David P. Novakovic

未读,
2010年5月24日 07:54:112010/5/24
收件人 python-...@googlegroups.com
Python sockets are closed when they are garbage collected - ie. when
they go out of scope.

Jefim

未读,
2010年5月24日 08:00:262010/5/24
收件人 Tornado Web Server
This does not mean memory leak, but the connection leak - the
connection is not closed

On May 24, 1:58 pm, "David P. Novakovic" <davidnovako...@gmail.com>
wrote:

Jefim

未读,
2010年5月24日 08:03:162010/5/24
收件人 Tornado Web Server
This does not mean memory leak, but the connection leak - the
connection is not closed

On May 24, 1:58 pm, "David P. Novakovic" <davidnovako...@gmail.com>
wrote:
回复全部
回复作者
转发
0 个新帖子