Jacob Perkins jap...@gmail.com added the comment:
Sorry about this. Turns out the flattening of memory usage was a temporary
coincidence, and I eventually tracked the bug down to an old version of MySQLdb.
--
resolution: - invalid
status: pending - closed
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Marked as pending since no further information is available. I will close this
issue in two weeks unless more information becomes available; even after this,
if you get more information, you can re-open this issue.
Also please note that
Changes by Éric Araujo mer...@netwok.org:
--
versions: +Python 2.7 -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12361
___
___
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
assignee: - vinay.sajip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12361
___
___
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Thanks for the report, but more information from the failing system may be
needed to find the problem. Although 2.6 does not contain full unit test
coverage, the default branch does - and I tested there with resource leak
checking turned
New submission from Jacob Perkins jap...@gmail.com:
I have a custom proxy server that was using a WatchedFileHandler for logging
requests (the files were rotated with logrotate). It was leaking memory, and I
had to use supervisord's memmon plugin to restart it whenever it exceed a
certain
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +vinay.sajip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12361
___
___
