[issue6653] Potential memory leak in multiprocessing

Antoine Pitrou added the comment: Closing as won't fix. -- resolution: -> wont fix stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ __

[issue6653] Potential memory leak in multiprocessing

Richard Oudkerk added the comment: I don't think this is a bug -- processes started with fork() should nearly always be exited with _exit(). And anyway, using sys.exit() does *not* guarantee that all deallocators will be called. To be sure of cleanup at exit you could use (the undocumented)

[issue6653] Potential memory leak in multiprocessing

Antoine Pitrou added the comment: Richard, do you think this is an actual concern? -- nosy: +pitrou, sbt versions: +Python 3.3, Python 3.4 -Python 3.1, Python 3.2 ___ Python tracker _

[issue6653] Potential memory leak in multiprocessing

Changes by Mark Lawrence : -- components: +Library (Lib) stage: -> needs patch type: -> resource usage versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ _

[issue6653] Potential memory leak in multiprocessing

Changes by Ask Solem : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue6653] Potential memory leak in multiprocessing

Changes by schlesin : -- nosy: +schlesin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue6653] Potential memory leak in multiprocessing

Jesse Noller added the comment: > In the future please use the bug tracker to file and track bugs with, > so things are not as lossy. Ok, sorry :) Also see Piet's comment here. He has a valid case against sys.exit in some cases. Thus it appears that both ways of shutting down child proces

[issue6653] Potential memory leak in multiprocessing

Jesse Noller added the comment: > Calling os.exit in a child process may be dangerous. It can cause > unflushed buffers to be flushed twice: once in the parent and once in > the child. I assume you mean sys.exit. If this is the case, multiprocessing needs a mechanism to chose between os._ex

[issue6653] Potential memory leak in multiprocessing

Changes by Jesse Noller : -- assignee: -> jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue6653] Potential memory leak in multiprocessing

Jesse Noller added the comment: Additional comments from Sturla: Hello Jesse, Yes there is a bug in multiprocessing. Diagnosis: - Processes created by multiprocessing (mp.Process or mp.Pool) exit in a way that prevents the Python interpreter from running deallocation code for all extension

[issue6653] Potential memory leak in multiprocessing

New submission from Jesse Noller : I have example code to show this. It creates a system-wide memory leak on Linux/Unix (present until the next reboot), unless the last statement in the target of mp.Process ensures a manual clean up of the globals. The problem is line 353 in multiprocessing/fo