Summary When running _testembed under LeakSanitizer, test_initconfig_get_api reports a memory leak.

Bug report

Bug description:

Summary

When running _testembed under LeakSanitizer,
test_initconfig_get_api reports a memory leak.

Reproducer

Build CPython with sanitizers:

./configure \
  --with-pydebug \
  --with-address-sanitizer \
  --with-undefined-behavior-sanitizer
make -j

Run the specific test:

ASAN_OPTIONS=detect_leaks=1 \
./Programs/_testembed test_initconfig_get_api

Observed result

LeakSanitizer reports:

ERROR: LeakSanitizer: detected memory leaks

Direct leak of 1 byte(s) in 1 object(s) allocated from:
    #0  malloc
    #1  PyInitConfig_GetStrList Python/initconfig.c:4024
    #2  test_initconfig_get_api Programs/_testembed.c:1844

Root cause

In test_initconfig_get_api:

1. The initial call to

PyInitConfig_GetStrList(config, "xoptions", &length, &items)

returns an empty list (length == 0).

2. The returned items buffer was not freed.
3. The PyInitConfig *config created by PyInitConfig_Create() was not released before returning.

Under LeakSanitizer, this results in a small direct leak and indirect leaks associated with the configuration lifetime.

Environment

• Architecture: aarch64-linux-gnu

• Built with: --with-address-sanitizer

• Leak detected via: ASAN_OPTIONS=detect_leaks=1

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-145206

Start in Programs/_testembed.c at test_initconfig_get_api and review the PyInitConfig_GetStrList result and configuration lifetime described in the report. Run the provided sanitizer build and ./Programs/_testembed test_initconfig_get_api; done means the test completes without LeakSanitizer reporting the direct or associated configuration leaks.