➜

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 christian.heimes
Recipients bkardon, christian.heimes, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-11-26.22:17:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574806676.83.0.0267029086994.issue38923@roundup.psfhosted.org>
In-reply-to
Content 
Good catch, Zach! A 32bit version of Python would certainly explain your problem. A 32bit process can only address 4 GB of address space. Almost half of the address space is reserved for OS, stack, Python itself, and other things. That leaves a little more than 2 GB of free heap memory for user data. Due to memory fragmentation it is possible that the allocator can't find a continuous free block 1 GB.
History
Date User Action Args
2019-11-26 22:17:56christian.heimessetrecipients: + christian.heimes, paul.moore, tim.golden, zach.ware, steve.dower, bkardon
2019-11-26 22:17:56christian.heimessetmessageid: <1574806676.83.0.0267029086994.issue38923@roundup.psfhosted.org>
2019-11-26 22:17:56christian.heimeslinkissue38923 messages
2019-11-26 22:17:56christian.heimescreate