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.

classification
Title: asyncio: reference leak in test_close_kill_running()
Type: Stage:
Components: asyncio Versions: Python 3.4, Python 3.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: gvanrossum, python-dev, vstinner, yselivanov
Priority: normal Keywords:

Created on 2015-02-17 21:40 by vstinner, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg236152 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-02-17 21:40
The test_close_kill_running() test of test.test_asyncio.test_subprocess leaks references. It may be a reference cycle.

----------------------
haypo@selma$ ./python -Wall -b -m test.regrtest -R 3:3:refleaks -m test_close_kill_running test_asyncio 
[1/1] test_asyncio
beginning 6 repetitions
123456
......
test_asyncio leaked [388, 388, 388] references, sum=1164
test_asyncio leaked [84, 85, 85] memory blocks, sum=254
1 test failed:
    test_asyncio
----------------------

See also the issue #23353.

Note: test_close_dont_kill_finished() doesn't leak.
msg236155 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2015-02-17 22:14
New changeset 0f6ddf944521 by Victor Stinner in branch '3.4':
Issue #23475, asyncio: Fix test_close_kill_running()
https://hg.python.org/cpython/rev/0f6ddf944521
History
Date User Action Args
2022-04-11 14:58:12adminsetgithub: 67663
2015-02-17 22:17:07vstinnersetstatus: open -> closed
resolution: fixed
2015-02-17 22:14:41python-devsetnosy: + python-dev
messages: + msg236155
2015-02-17 21:40:00vstinnercreate