Bug report

Bug description:

Since67807cf,_testembed.exe (x64 Release) increases the memory usage in the cycle ofPy_Initialize andPy_Finalize.

I monitored the Task Manager (taskmgr.exe) on Windows10/11, with a change againstPrograms/_testembed.c:

-#defineINIT_LOOPS 4+#defineINIT_LOOPS 200

Commands:

• _testembed.exe test_repeated_simple_init or
• python -m test test_embed -m test_simple_initialization_api (no log)

With RADIX TREE (as-is)

No RADIX TREE (as-is)

Recentobmalloc.c looks ready for finalization. Just adding my rough (invalid?) experiment made the leaks even. So, I hope that they share the same issue. Otherwise,ea2c001 or15d4c9f has another leak.#98359 (comment)

void_PyInterpreterState_FinalizeAllocatedBlocks(PyInterpreterState*interp){if (has_own_state(interp)) {Py_ssize_tleaked=_PyInterpreterState_GetAllocatedBlocks(interp);assert(has_own_state(interp)||leaked==0);interp->runtime->obmalloc.interpreter_leaks+=leaked;+OMState*state=&interp->obmalloc;+for (uinti=0;i<maxarenas;++i) {+if (allarenas[i].address==0) {+continue;+           }+_PyObject_Arena.free(_PyObject_Arena.ctx,+                                (void*)allarenas[i].address,ARENA_SIZE);+allarenas[i].address=0;+--narenas_currently_allocated;+       }+PyMem_RawFree(allarenas);    }}

With RADIX TREE (patched)

No RADIX TREE (patched)

cc@ericsnowcurrently@nascheme

CPython versions tested on:

3.12, 3.13, CPython main branch:3aea6c4

Operating systems tested on:

Windows

Linked PRs

• gh-113055: Fix memory leak of obmalloc state #113218
• gh-113055: Use pointer for interp->obmalloc state. #113412
• gh-118608: datetime: Fix use-after-free on embedded CPython #118531
• [3.12]: gh-113055: Use pointer for interp->obmalloc state #118618