Augusto Mecking Caringi wrote:
> >>> om[3082188716].c
[…]
> str(2917687304
> 53120905B 1par 'ype: Test\nDate: 2011-12-14
> 16:45:30.995217\nEvent-Subtype: FooBar\nContent-Type:
> application/json\n\n{\n ')So it appears you have 53 megabyte string that's referenced from your TLS connection, presumably in a buffer of data waiting to be sent? At the moment this memory analysis was captured, do you know how much of this data the client has received? Also, how was this data passed to the transport — in one big 53MB write call, or via many smaller calls, or via a pull producer, or…? This looks like an HTTP-like protocol, so possibly there's a library between your code and the transport that means you don't know the direct answer to that question. But whatever details you can give about how you are passing the data you generate to the connection will help locate the problem, I think. -Andrew. _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
