+ "notes": "Assertion bug: fires only on assertion-enabled builds (ft_debug_asan/gil_debug_asan/jit abort at dictobject.c:5532). ft_release=n/a (NDEBUG strips assert; no segv on that run). Release builds segv at the untrack: upstream (release-gil-nojit) segv rc139 in _Py_Dealloc via PyObject_GetIter; release-gil-nojit-asan ASan SEGV at _PyObject_GC_UNTRACK (identical frames) -- NDEBUG corrupts the GC list instead of asserting; this is why the zipapp vehicle was labeled 'segfault' yet trips the identical dictiter assert on the debug build (verified). Only item iterators affected (dict_itemiterator) -- only kind whose di_result needs an alloc between PyObject_GC_New and _PyObject_GC_TRACK. TWO repros: (1) repro.py = realistic stdlib path `_strptime._strptime('', '')` under the set_nomemory sweep (this is the form published in the gist); (2) repro_direct.py = DIRECT minimal, stdlib-only, no _strptime (deterministic, re-verified 8/8 on ft_debug_asan @1b9fe5c, crashes ~start=2): iter(d.items()) under the sweep after draining the size-2 tuple freelist (hold a list of live 2-tuples) so di_result's _PyTuple_FromPairSteal actually hits the failing allocator; uses the iter() builtin (not GET_ITER) to avoid the adjacent PyStackRef_XCLOSE negrefcount bug; range(16) covers the per-build offset. The earlier 'minimization: partial' assumed a warm pymalloc/freelist steady state -- the freelist drain (plus the ASan triage builds being --without-pymalloc, so PyObject_GC_New is already counted) is the missing trick; minimization is now COMPLETE. signature/backtrace.txt unchanged: iter() reaches the SAME dictiter_new->Py_DECREF->dictiter_dealloc defect frames as the vehicle's GET_ITER path. repro_direct.py from another instance's handoff, independently re-verified (8/8 abort on ft_debug_asan; no-drain control = no crash; release-gil-nojit-asan SEGV confirmed). UPSTREAM: this bug is python/cpython#152107 (a pre-existing INDEPENDENT report, not ours); the simplified repro_direct.py was posted there 2026-06-24 and acked by the issue author. status=reported reflects that upstream issue (we also have the older gist)."
0 commit comments