➜

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 snordhausen
Recipients christian.heimes, serhiy.storchaka, snordhausen
Date 2017-12-19.12:41:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513687260.18.0.213398074469.issue32368@psf.upfronthosting.co.za>
In-reply-to
Content 
I tried out PR 3015 of Serhiy and this fixes the segfaults. So it seems to be a duplicate.

As for backporting the fix: Is this a 'reliable' segfault (i.e. it always segfaults when the limit is exceeded) or could there be some silent data corruption? If data can be corrupted, I'd consider this bug very serious, otherwise it's a rather small annoyance.
History
Date User Action Args
2017-12-19 12:41:00snordhausensetrecipients: + snordhausen, christian.heimes, serhiy.storchaka
2017-12-19 12:41:00snordhausensetmessageid: <1513687260.18.0.213398074469.issue32368@psf.upfronthosting.co.za>
2017-12-19 12:41:00snordhausenlinkissue32368 messages
2017-12-19 12:41:00snordhausencreate