René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"concurrent.futures.ThreadPoolExecutor does not free memory when shutdown ","articleBody":"# Bug report\r\n\r\nMemory allocated in threads is never freed when using a ThreadPoolExecutor.   The expected behavior is that when the executor is shut down, all memory allocated in its threads should be freed.  The below code demonstrates this leak in that the the memory usage before allocating memory in threads is significantly less than after.  \r\n\r\n```python\r\nfrom concurrent.futures import ThreadPoolExecutor, as_completed\r\nimport resource\r\n\r\ndef process_user(x):\r\n    return bytearray(10000000) \r\n\r\nprint('Before', resource.getrusage(resource.RUSAGE_SELF).ru_maxrss/1024, 'MB')\r\n\r\ndef leak_memory():\r\n    with ThreadPoolExecutor(max_workers=20) as executor:\r\n        futures = [executor.submit(process_user, i) for i in range(100)]\r\n        for future in as_completed(futures):\r\n            cur = resource.getrusage(resource.RUSAGE_SELF).ru_maxrss/1024\r\n            print('Step', cur)\r\n\r\nleak_memory()\r\n\r\nprint('After', resource.getrusage(resource.RUSAGE_SELF).ru_maxrss/1024, 'MB')\r\n```\r\n\r\n# Your environment\r\n\r\nPython 3.9.x/3.10.x.  Mac os and debian.\r\n\r\n","author":{"url":"https://github.com/eMeena","@type":"Person","name":"eMeena"},"datePublished":"2022-10-19T21:30:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/98467/cpython/issues/98467"}