Much like bpo-9366 the same file can be used. This reference leaks according to Nuitka comparative testing:

simpleFunction59: FAILED 129511 129512 leaked 1

def simpleFunction59():
    a = 3
    b = 5

try:
    a = a * 2

        return a
    finally:
        return a / b

I would be guessing, that you are leaking the return value when returning again.

New changeset 4d29983 by Victor Stinner in branch 'master':
bpo-36725: regrtest: add TestResult type (GH-12960)
4d29983

New changeset 3cde440 by Victor Stinner in branch 'master':
bpo-36725: Refactor regrtest multiprocessing code (GH-12961)
3cde440

Sorry, the two commits are related to bpo-36719 not to this issue.

I wrote an unit test to be able to re-use regrtest memory leak hunter:

import unittest

def simpleFunction59():
    a = 1
    try:
        return a
    finally:
        return a

class Tests(unittest.TestCase):
    def test_bug(self):
        for _ in range(10):
            simpleFunction59()

I confirm that there is a leak:

$ ./python -m test -R 3:3 test_bug
...
test_bug leaked [10, 10, 10] references, sum=30
...

New changeset 1069d38 by Victor Stinner in branch '3.7':
[3.7] bpo-36719: sync regrtest with master branch (GH-12967)
1069d38

Let me work on this.

@ victor, I have tried your example but I can not reproduce the leak as you did above. May be am missing something?

I used some other tool and got this summary when I was investigating this:

                        types |   # objects |   total size

================================= | =========== | ============
<class 'str | 3916 | 361.40 KB
<class 'list | 2513 | 237.41 KB
<class 'dict | 197 | 120.28 KB
<class 'code | 617 | 86.79 KB
<class 'type | 81 | 80.71 KB
<class 'int | 497 | 13.60 KB
<class 'tuple | 199 | 12.80 KB
function (init) | 61 | 8.10 KB
<class 'weakref | 87 | 6.80 KB
<class 'getset_descriptor | 67 | 4.71 KB
<class 'collections.OrderedDict | 3 | 4.22 KB
<class 'enum.EnumMeta | 3 | 2.98 KB
function (call) | 14 | 1.86 KB
<class 'cell | 37 | 1.73 KB
<enum 'Signals | 32 | 1.62 KB

Am still investigating though.

I am able to reproduce it finally.

Run tests sequentially
0:00:00 load avg: 0.21 [1/1] test_bug
beginning 6 repetitions
123456
......
test_bug leaked [10, 10, 10] references, sum=30
test_bug failed

== Tests result: FAILURE ==

1 test failed:
test_bug

Total duration: 220 ms
Tests result: FAILURE

This leak has been fixed by:

commit f00828a (refs/bisect/bad)
Author: Pablo Galindo <Pablogsal@gmail.com>
Date: Thu May 9 16:52:02 2019 +0100

bpo-36851: Clean the frame stack if the execution ends with a return and the stack is not empty (GH-13191)