This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients serhiy.storchaka, vstinner, xdegaye
Date 2017-06-19.13:28:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The chain of events following a call to set_nomemory_allocator() is deterministic, this is another difference with pyfailmalloc. Also what happens then after this call is not very close to real life as memory is never freed.

Having the possibility to trigger memory exhaustion in N allocations instead of rightaway would be very useful. Maybe this could be done by including pyfailmalloc in _testcapi with some changes to enable multiple behaviors, among which one of them would be deterministic.
Date User Action Args
2017-06-19 13:28:23xdegayesetrecipients: + xdegaye, vstinner, serhiy.storchaka
2017-06-19 13:28:23xdegayesetmessageid: <>
2017-06-19 13:28:23xdegayelinkissue30695 messages
2017-06-19 13:28:23xdegayecreate