BPO | [28195](https://bugs.python.org/issue28195) --- | :--- Nosy | @vstinner, @benjaminp, @berkerpeksag *Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.* Show more details GitHub fields: ```python assignee = None closed_at = created_at = labels = ['3.7', 'type-bug', 'tests'] title = 'test_huntrleaks_fd_leak fails on Windows' updated_at = user = 'https://github.com/berkerpeksag' ``` bugs.python.org fields: ```python activity = actor = 'berker.peksag' assignee = 'none' closed = True closed_date = closer = 'vstinner' components = ['Tests'] creation = creator = 'berker.peksag' dependencies = [] files = [] hgrepos = [] issue_num = 28195 keywords = [] message_count = 7.0 messages = ['276878', '276883', '276920', '276923', '276925', '276968', '276969'] nosy_count = 4.0 nosy_names = ['vstinner', 'benjamin.peterson', 'python-dev', 'berker.peksag'] pr_nums = [] priority = 'normal' resolution = 'fixed' stage = 'resolved' status = 'closed' superseder = None type = 'behavior' url = 'https://bugs.python.org/issue28195' versions = ['Python 3.6', 'Python 3.7'] ```
Activity
berkerpeksag commentedon Sep 18, 2016
From http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/11654/steps/test/logs/stdio
======================================================================
FAIL: test_huntrleaks_fd_leak (test.test_regrtest.ArgsTestCase)
----------------------------------------------------------------------
berkerpeksag commentedon Sep 18, 2016
It looks like http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/11581 is first time that the test was failed.
Revisions (without documentation changes) in that build:
python-dev commentedon Sep 18, 2016
New changeset 91285b24f1c2 by Victor Stinner in branch '3.6':
Fix test_huntrleaks_fd_leak() of test_regrtest
https://hg.python.org/cpython/rev/91285b24f1c2
vstinner commentedon Sep 18, 2016
I modified the test_regrtest unit test because the test is too fragile, it expects a line on a specific line number.
But there is still a real memory leak detected by this unit test.
vstinner commentedon Sep 18, 2016
Ah, I found a leak: see issue bpo-28200.
vstinner commentedon Sep 19, 2016
FYI there was a real memory leak and I just fixed it with the change 6232e610e310.
berkerpeksag commentedon Sep 19, 2016
Thanks Victor!