COUNT_ALLOCS
------------

Each type object grows three new members:

    /* Number of times an object of this type was allocated. */
    int tp_allocs;

    /* Number of times an object of this type was deallocated. */
    int tp_frees;

    /* Highwater mark:  the maximum value of tp_allocs - tp_frees so
     * far; or, IOW, the largest number of objects of this type alive at
     * the same time.
     */
    int tp_maxalloc;



Following patches are part of enabling COUNT_ALLOCS at build time:

Adding option to enable COUNT_ALLOCS to configure as COUNT_ALLOCS is only documented feature, there is no flag to enable it in upstream:
 00113-more-configuration-flags.patch

Enabling verbose output of COUNT_ALLOCS only when env variable PYTHONDUMPCOUNTS is enabled:
 00125-less-verbose-COUNT_ALLOCS.patch

Skipping tests when COUNT_ALLOCS is enabled:
 00134-fix-COUNT_ALLOCS-failure-in-test_sys.patch
 00135-fix-test-within-test_weakref-in-debug-build.patch
 00141-fix-tests_with_COUNT_ALLOCS.patch

Upstream report for skipping tests when COUNT_ALLOCS is enabled:

http://bugs.python.org/issue19527


Reply from Dave Malcolm:
"""
My hazy recollection is that at the time I was dealing with lots of
memory leak issues in Python 2, so I was keen to add as much help as
possible in tracking them down to Python 2 and Python 3.

I don't think this patch ever really bought us much, and it sounds like
there are better tools for this now, so feel free to drop the
COUNT_ALLOC patches.
"""