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: test_type_comments leaks references and memory blocks
Type: Stage: resolved
Components: Interpreter Core, Tests Versions: Python 3.8
process
Status: closed Resolution: duplicate
Dependencies: Superseder: test_type_comments leaks references
View: 35879
Assigned To: Nosy List: gvanrossum, lukasz.langa, pablogsal, vstinner, xtreak
Priority: normal Keywords:

Created on 2019-02-01 14:02 by pablogsal, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (5)
msg334676 - (view) Author: Pablo Galindo Salgado (pablogsal) * (Python committer) Date: 2019-02-01 14:02
The refleak buildbots have detected that test_type_comments is leaking references. Example failure:

https://buildbot.python.org/all/#/builders/1/builds/490/steps/4/logs/stdio

test_type_comments leaked [37, 37, 37] references, sum=111
test_type_comments leaked [11, 12, 11] memory blocks, sum=34
1 test failed again:
    test_type_comments

Bisecting shows that PR11645 is the one that introduced the refleaks:

https://github.com/python/cpython/pull/11645/files#

After some hours of debugging, I have identified the (possible) cause of the majority of the refleaks. 

The type_comments created in ast.c with new_type_comment() never reaches 0 reference counts. This **seems** to be because the cleanup for the stmt_ty elements where the type_comments are included never call DECREF on these elements when destroyed unless I am missing something fundamental.
msg334679 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2019-02-01 14:07
This looks like the same as https://bugs.python.org/issue35879
msg334680 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-02-01 14:08
> This looks like the same as https://bugs.python.org/issue35879

Yeah, as usual Pablo is way too slow: he posted the same bug 1h30 after me.
msg334681 - (view) Author: Pablo Galindo Salgado (pablogsal) * (Python committer) Date: 2019-02-01 14:11
> Yeah, as usual, Pablo is way too slow: he posted the same bug 1h30 after me.

:(
msg334686 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-02-01 15:14
> :(

I'm kidding :-) Sorry for not reviewing emails from buildbot-status.
History
Date User Action Args
2022-04-11 14:59:10adminsetgithub: 80062
2019-02-01 15:14:41vstinnersetmessages: + msg334686
2019-02-01 14:11:08pablogsalsetmessages: + msg334681
2019-02-01 14:09:03vstinnersetstatus: open -> closed
superseder: test_type_comments leaks references
resolution: duplicate
stage: resolved
2019-02-01 14:08:33vstinnersetmessages: + msg334680
2019-02-01 14:07:19xtreaksetnosy: + xtreak, vstinner
messages: + msg334679
2019-02-01 14:02:45pablogsalcreate