Daniel W Forsyth added the comment:
The only way I could figure out to control it was to do this in a thread;
for thread in server._threads: # type: Thread
if not thread.is_alive():
server._threads.remove(thread)
Shouldn't the server process do this when
STINNER Victor added the comment:
This issue is a duplicate of bpo-37193.
--
nosy: +vstinner
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Memory leak while running TCP/UDPServer with
socketserver.ThreadingMixIn
New submission from Daniel W Forsyth :
After putting a basic ThreadingUDPServer under load (500 messages per/second)
I noticed that after a night it was consuming a lot of RAM given it does
nothing with the data.
On inception, I noticed the _thread count inside the server was growing
