Message 296331 - Python tracker

➜

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.

In-reply-to
Author	xdegaye
Recipients	serhiy.storchaka, vstinner, xdegaye
Date	2017年06月19日.13:28:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1497878903.24.0.267863085242.issue30695@psf.upfronthosting.co.za>

Content
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.

Content

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.

History
Date	User	Action	Args
2017年06月19日 13:28:23	xdegaye	set	recipients: + xdegaye, vstinner, serhiy.storchaka
2017年06月19日 13:28:23	xdegaye	set	messageid: <1497878903.24.0.267863085242.issue30695@psf.upfronthosting.co.za>
2017年06月19日 13:28:23	xdegaye	link	issue30695 messages
2017年06月19日 13:28:23	xdegaye	create

homepage