[issue37389] Memory Leak - ThreadingUDPServer

2019-06-24 Thread Daniel W Forsyth


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 the thread is done?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37389] Memory Leak - ThreadingUDPServer

2019-06-24 Thread STINNER Victor


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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37389] Memory Leak - ThreadingUDPServer

2019-06-24 Thread Daniel W Forsyth


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 forever 
even though the sub-threads are done.

Setup a basic ThreadingUDPSever with handler that does nothing and check the 
request_queue_size, it seems to grow without limit.

--
components: Library (Lib)
messages: 346410
nosy: d...@dataforge.on.ca
priority: normal
severity: normal
status: open
title: Memory Leak - ThreadingUDPServer
type: performance
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com