[issue1517495] memory leak threading or socketserver module

A.M. Kuchling added the comment: I can no longer confirm this bug, either; trying the scripts with the current trunk doesn't seem to leak. Backing out Jeffrey's r61011 didn't bring the problem back, so I'll just conclude that the problem has gotten fixed along the way somehow. -- re

[issue1517495] memory leak threading or socketserver module

Changes by Robert Schuppenies <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file9942/memory2.6a2.csv _ Tracker <[EMAIL PROTECTED]> _ __

[issue1517495] memory leak threading or socketserver module

Robert Schuppenies <[EMAIL PROTECTED]> added the comment: I can *not* confirm the leak. I tested using the provided scripts (with little modifications to log memory usage), using 1000 instead of 20 runs. I am running on Debian Linux and checked the reported Python 2.4.2 and the current trunk (2.6

[issue1517495] memory leak threading or socketserver module

Jeffrey Yasskin added the comment: It's possible but unlikely that r61011 fixed this. SocketServer creates the reference cycles it fixed, but they tended to get cleaned up by gc.collect(), so it sounds like that wasn't the bug you're seeing here. I haven't had time yet to check, so I'm mentioning