50e6e991781db761c496561a995541ca8d83ff87 causes or exposes a
leak. Possibly the leak was there before but showed up under
"still reachable".

Now it is "definitely lost", so tstate->interp->ceval.pending
needs to be cleaned up.


==11235== 32 bytes in 1 blocks are definitely lost in loss record 186 of 1,901
==11235==    at 0x483880B: malloc (vg_replace_malloc.c:309)
==11235==    by 0x467061: _PyMem_RawMalloc (obmalloc.c:99)
==11235==    by 0x467A24: PyMem_RawMalloc (obmalloc.c:572)
==11235==    by 0x528599: PyThread_allocate_lock (thread_pthread.h:379)
==11235==    by 0x4C69B3: _PyEval_InitThreads (ceval.c:231)
==11235==    by 0x50F1EE: pycore_create_interpreter (pylifecycle.c:560)
==11235==    by 0x50FB8A: pyinit_config (pylifecycle.c:756)
==11235==    by 0x5102F7: pyinit_core (pylifecycle.c:923)
==11235==    by 0x510D7A: Py_InitializeFromConfig (pylifecycle.c:1133)
==11235==    by 0x41DAF1: pymain_init (main.c:66)
==11235==    by 0x41EB04: pymain_main (main.c:653)
==11235==    by 0x41EBAD: Py_BytesMain (main.c:686)
==11235==