[issue29041] Reference leaks on Windows

2017-10-02 Thread STINNER Victor
STINNER Victor added the comment: > Victor has cleaned these up, and we now have a buildbot running refleak > checks on Windows every day (as long as it's not hung :) \o/ Hopefully I was alone ;-) https://haypo.github.io/contrib-cpython-2017q2-part2.html --

[issue29041] Reference leaks on Windows

2017-09-30 Thread Zachary Ware
Zachary Ware added the comment: Victor has cleaned these up, and we now have a buildbot running refleak checks on Windows every day (as long as it's not hung :) -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed

[issue29041] Reference leaks on Windows

2017-04-17 Thread Zachary Ware
Zachary Ware added the comment: Here's an updated refleak run, on master as of last Thursday: test_atexit leaked [12, 12, 12] references, sum=36 test_atexit leaked [4, 6, 6] memory blocks, sum=16 test_capi leaked [6, 6, 6] references, sum=18 test_capi leaked [2, 4, 4] memory blocks, sum=10

[issue29041] Reference leaks on Windows

2016-12-21 Thread Zachary Ware
New submission from Zachary Ware: Discussion in #29034 inspired me to run a refleak check on Windows, with the following results from a 32-bit build of the current 3.6 branch: C:\cpython\3.6>PCbuild\build.bat -e -d C:\cpython\3.6>python -m test -uall -R 3:3:refleak_log.txt --timeout=7200 ...