@ZeroIntensity, I've fixed all those Docs things.

Good point. It would make sense to automatically call it for users.

@brianquinlan, what are your thoughts on this?

@brianquinlan, what are your thoughts on this?

@ericsnowcurrently I haven't been active for yours but this seems like an excellent addition.

This may have introduced arefleak crash on one of the refleak buildbots:https://buildbot.python.org/#/builders/259/builds/1528. I'm taking a look.

Yeah, I noticed the tests forInterpreterPoolExecutor segfaulting on someone elses PR yesterday on something seemingly unrelated. Since this is pure-Python,_interpreters might be buggier than we think :(

In the crash I linked to, it happened when calling_interpqueues.create(), so not_interpreters.

FWIW, the only other failure I've seen with this on refleak buildbots isAMD64 FreeBSD Refleaks 3.x, with 3 successful runs afterone failure, which looks like it hung.

The other one I mentioned was onAMD64 RHEL8 Refleaks 3.x, and has had multiple successful runs to go with that one crash.

I don't see any other failures for this on other stable buildbots.

I also haven't been able to reproduce any crash or hang locally yet.

I guess it's possible that this only affects AMD?

It's probably a race due to some load profile that has only shown up there.

I'll run the tests under valgrind to see if it picks anything up. That will take a while, though. Do you want to revert this in the meantime?

Ah,@ericsnowcurrently, I think I found the problem. In most of the_interpqueues methods, something like this is passed toPyArg* as a converter:

qidarg_converter_data qidarg;

As far as I can tell, default struct initialization is not C standard, so it's values are just junk stack memory. I'm guessing that x86 has some sort of detail that sets stack-allocated structs to NULL, but not on ARM--that's why it's only failing there.

Edit: Oh wait, it's AMD, not ARM. I guess it's a chip-specific issue then, but the point is that it's UB.

Hmm, I'll take a look.

Yeah, that could very well be it. The "label" field would sometimes be a problem if not initialized. I'll fix that.

I've openedgh-125667.

Great, I'll review your PR whenever you get to it.

gh-125668

I also noticed a failure on the Android buildbot:https://buildbot.python.org/#/builders/1594/builds/338. I'm looking into it.

#125708

Looks like there's more to do:https://buildbot.python.org/#/builders/1610/builds/198 (AMD64 CentOS9 NoGIL Refleaks). I'm looking into it.

I've opened a new issue to deal with this, so we don't keep going on here:#125716.