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 jkloth
Recipients barry, jkloth, r.david.murray, vstinner
Date 2017-05-16.22:33:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494974001.49.0.600976437334.issue30371@psf.upfronthosting.co.za>
In-reply-to
Content
My thinking is that in normal running, the in-use memory is below the bad bit.  It is due to that test using such a large chunk of memory that it pushes the data into the bad area.  I would wager that if largemem tests were run, the would error as well.
History
Date User Action Args
2017-05-16 22:33:21jklothsetrecipients: + jkloth, barry, vstinner, r.david.murray
2017-05-16 22:33:21jklothsetmessageid: <1494974001.49.0.600976437334.issue30371@psf.upfronthosting.co.za>
2017-05-16 22:33:21jklothlinkissue30371 messages
2017-05-16 22:33:21jklothcreate