> These leaks have been here a while. Anyone know the cause?
>
> On Tue, 20 Oct 2015 at 01:47 <solipsis at pitrou.net> wrote:
>
>> results for d7e490db8d54 on branch "default"
>> --------------------------------------------
>>
>> test_capi leaked [5411, 5411, 5411] references, sum=16233
>> test_capi leaked [1421, 1423, 1423] memory blocks, sum=4267
>> test_functools leaked [0, 2, 2] memory blocks, sum=4
>> test_threading leaked [10820, 10820, 10820] references, sum=32460
>> test_threading leaked [2842, 2844, 2844] memory blocks, sum=8530
Bisection shows they were probably introduced by:
changeset: 97413:dccc4e63aef5
user: Raymond Hettinger <pyt...@rcn.com>
date: Sun Aug 16 19:43:34 2015 -0700
files: Doc/library/operator.rst Doc/whatsnew/3.6.rst
Lib/operator.py Lib/test/test_operator.py
description:
Issue #24379: Add operator.subscript() as a convenience for building slices.
If you comment out `@object.__new__` on line 411 in operator.py, or if
you remove the __slots__ assignment (which is a bit worrying), the leak
seems suppressed.
You can reproduce using:
$ ./python -m test -m SubinterpreterTest -R 3:3 test_capi
[1/1] test_capi
beginning 6 repetitions
123456
......
test_capi leaked [5443, 5443, 5443] references, sum=16329
test_capi leaked [1432, 1434, 1434] memory blocks, sum=4300
1 test failed:
test_capi
Regards
Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
