[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Stefan Krah]

Stefan Krah <stefan at bytereef.org> added the comment:

No, it does not cause real issues. Adding this feature would just suppress chatty diagnostics like this one, which are a bit unfriendly: 

>>> [0] * 10000000000000000
python3(36633,0x110c08dc0) malloc: can't allocate region
:*** mach_vm_map(size=80000000000004096, flags: 100) failed (error code=3)
python3(36633,0x110c08dc0) malloc: *** set a breakpoint in malloc_error_break to debug
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
MemoryError


So yes, users do occasionally see it outside the test suite.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue40928>
_______________________________________