[issue21116] Failure to create multiprocessing shared arrays larger than 50% of memory size under linux

Charles-François Natali report at bugs.python.org
Thu Apr 3 08:14:09 CEST 2014


Charles-François Natali added the comment:

> If I remember correctly the problem is that some OS like linux (and
probably others) do not really allocate space until something is written.
If that's the case then the process may get killed later on when it writes
something in the array.

Yes, it's called overcommitting, and it's a good thing. It's exactly the
same thing for memory: malloc() can return non-NULL, and the process will
get killed when first writing to the page in case of memory pressure.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21116>
_______________________________________


More information about the Python-bugs-list mailing list