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 pitrou
Recipients brian.curtin, loewis, neologix, pitrou, tim.golden
Date 2013-05-22.17:24:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I asked for benchmarks because I don't know anything about Windows virtual memory management, but if other people think this patch should go in then it's fine.

The main point of using VirtualAlloc/VirtualFree was, in my mind, to allow *releasing* memory in more cases than when relying on free() (assuming Windows uses some sbrk() equivalent). But perhaps Windows is already tuned to release memory on most free() calls.
Date User Action Args
2013-05-22 17:24:57pitrousetrecipients: + pitrou, loewis, tim.golden, brian.curtin, neologix
2013-05-22 17:24:57pitrousetmessageid: <>
2013-05-22 17:24:57pitroulinkissue13483 messages
2013-05-22 17:24:57pitroucreate