STINNER Victor <vstin...@redhat.com> added the comment:
It doesn't look like a real leak, but more a cache which takes multiple
iterations to be fully filled.
pydev@stormageddon ~/cpython $ ./python -m test test_multiprocessing_spawn -m
test.test_multiprocessing_spawn.WithProcessesTestPool.test_imap_unordered -R
1:30
WARNING: Running tests with --huntrleaks/-R and less than 3 warmup repetitions
can give false positives!
Run tests sequentially
0:00:00 load avg: 0.88 [1/1] test_multiprocessing_spawn
beginning 31 repetitions
1234567890123456789012345678901
...............................
test_multiprocessing_spawn leaked [4, 5, 1, 5, 1, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] memory blocks, sum=18
test_multiprocessing_spawn failed in 42 sec 470 ms
== Tests result: FAILURE ==
1 test failed:
test_multiprocessing_spawn
Total duration: 42 sec 490 ms
Tests result: FAILURE
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue33735>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
