Re: [Twisted-Python] memory leaks

> On Dec 6, 2016, at 3:17 AM, bret curtis wrote: > > Isn't this a duplicate of my "memory leak" bug report from about 11 months > ago? > https://twistedmatrix.com/trac/ticket/8164 Yes, thank you for the reference to that. I've closed the new one and updated the old one. >

Re: [Twisted-Python] memory leaks

Isn't this a duplicate of my "memory leak" bug report from about 11 months ago? https://twistedmatrix.com/trac/ticket/8164 Glype's last comment on the ticket was: Now, again, I want to be clear that the buffer size here is still a bug, and we vastly mis-estimated a reasonable size. The end

Re: [Twisted-Python] memory leaks

> On Dec 5, 2016, at 10:18 PM, Amber Hawkie Brown > wrote: > > >> On 6 Dec. 2016, at 17:09, Glyph Lefkowitz > > wrote: >> >> >> twisted.logger._initialBuffer can consume a surprisingly large amount of >>

Re: [Twisted-Python] memory leaks

> On 6 Dec. 2016, at 17:09, Glyph Lefkowitz wrote: > > > twisted.logger._initialBuffer can consume a surprisingly large amount of > memory if logging is not initialized > > > The way that `twisted.logger` is supposed to work is that at process startup > time, the

Re: [Twisted-Python] memory leaks

> On Dec 4, 2016, at 9:50 AM, Jean-Paul Calderone > wrote: > > On Sun, Dec 4, 2016 at 12:50 AM, Glyph Lefkowitz > wrote: > Following up on a Stack Overflow question from some time ago, >

Re: [Twisted-Python] memory leaks

On Sun, Dec 4, 2016 at 12:50 AM, Glyph Lefkowitz wrote: > Following up on a Stack Overflow question from some time ago, > http://stackoverflow.com/questions/40604545/twisted- > using-connectprotocol-to-connect-endpoint-cause-memory-leak?noredirect=1# >

[Twisted-Python] memory leaks

Following up on a Stack Overflow question from some time ago, http://stackoverflow.com/questions/40604545/twisted-using-connectprotocol-to-connect-endpoint-cause-memory-leak?noredirect=1#comment68573508_40604545 since the submitter added a minimal reproducer, I used Heappy