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 ebfe
Recipients benjamin.peterson, christian.heimes, ctheune, ebfe, gvanrossum, hynek
Date 2012-11-02.15:10:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351869024.77.0.840710489486.issue16381@psf.upfronthosting.co.za>
In-reply-to
Content
The heuristic basically has to decide if memory pressure is so high that it's not save to return to the interpreter. Even if there is a chosen value (e.g. failed allocation attempts below 1mb are considered fatal), there can always be another OS-thread in the interpreter process that eats away exactly that memory while we are returning MemoryError - the program might still hang.
FWICS all MemoryErrors are to be considered fatal or none of them
History
Date User Action Args
2012-11-02 15:10:24ebfesetrecipients: + ebfe, gvanrossum, ctheune, christian.heimes, benjamin.peterson, hynek
2012-11-02 15:10:24ebfesetmessageid: <1351869024.77.0.840710489486.issue16381@psf.upfronthosting.co.za>
2012-11-02 15:10:24ebfelinkissue16381 messages
2012-11-02 15:10:24ebfecreate