🤖 New build scheduled with the buildbot fleet by @JelleZijlstra for commit 3c448e8 🤖

If you want to schedule another build, you need to add the 🔨 test-with-refleak-buildbots label again.

This is also wrong, trying to figure out the right way to handle the refcounting here now.

The problem is that the way we need to manage the refcount on mod_or_class_dict is different for the two instructions that use the _LOAD_FROM_DICT_OR_GLOBALS op: in the LOAD_NAME case, we own the only reference to the dict, so we need to decref it in all cases, including the error conditions. But in the LOAD_FROM_DICT_OR_GLOBALS case, the dict is still on the stack until the end of the instruction, so in the error case, it gets decrefed automatically during stack unwinding. The code that is currently in main is correct for the LOAD_NAME case, but we get a double decref for the goto error branches. The code in my initial PR is correct for LOAD_FROM_DICT_OR_GLOBALS, but it doesn't DECREF properly in the error case for LOAD_NAME, so we leak references.

I couldn't figure out how to get the refcounting right in both cases with the existing macros, so I got rid of the macros and duplicated the code instead, which made it possible to get the correct refcounting in both conditions.

🤖 New build scheduled with the buildbot fleet by @JelleZijlstra for commit 882ada7 🤖

If you want to schedule another build, you need to add the 🔨 test-with-refleak-buildbots label again.

A few buildbots are now segfaulting on test_sys_settrace. Doesn't reproduce locally on macOS.

The buildbot failures seem unrelated, filed #109143.

Thanks for the review! Yes, there's probably a way to get this to work, but especially since the cases generator is quite different on main and on 3.12 by now, it's probably better to accept the code duplication and go with my current solution.

I think this is just a bug in the cases generator; it should realize in the macro() case that it needs to account for where the input actually came from in the previous uop when it is deciding how many items need to be popped off the stack at an ERROR_IF. cc @gvanrossum to confirm or contradict my analysis here.

Oh dear. I'm afraid I've been deep into other things, and it'll take me some time to confirm this.

But given that we want to minimize risk at this point, it may be best (at least for 3.12) to go with this code-duplication fix rather than trying to make changes to the cases generator.

That definitely feels like the safest approach -- a fix to the cases generator likely can't be backported, since the version on main was extensively refactored during the rc phase.

Thanks @JelleZijlstra for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

Sorry, @JelleZijlstra, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 17f994174de9211b2baaff217eeb1033343230fc 3.12

GH-109173 is a backport of this pull request to the 3.12 branch.