[issue21810] SIGSEGV in PyObject_Malloc when ARENAS_USE_MMAP

2014-06-19 Thread John-Mark Bell
New submission from John-Mark Bell: In low-memory scenarios, the Python 2.7 interpreter may crash as a result of failing to correctly check the return value from mmap in new_arena(). This changeset appears to be the point at which this issue was introduced:

[issue21810] SIGSEGV in PyObject_Malloc when ARENAS_USE_MMAP

2014-06-19 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +benjamin.peterson, neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21810 ___ ___

[issue21810] SIGSEGV in PyObject_Malloc when ARENAS_USE_MMAP

2014-06-19 Thread Roundup Robot
Roundup Robot added the comment: New changeset 012b5c9c062d by Charles-François Natali in branch '2.7': Issue #21810: Backport mmap-based arena allocation failure check. http://hg.python.org/cpython/rev/012b5c9c062d -- nosy: +python-dev ___ Python

[issue21810] SIGSEGV in PyObject_Malloc when ARENAS_USE_MMAP

2014-06-19 Thread Charles-François Natali
Charles-François Natali added the comment: Thanks for the report. The patch introducing mmap() to limit memory fragmentation was applied initially only to the Python 3 branch (3.2 at that time IIRC). This problem was spotted a couple days later, and fixed: