Daniel Alley added the comment:
A helpful user in the discord was able to point out where the bug was - in our
extension, but not directly apparent from the valgrind output.
--
resolution: -> not a bug
stage: -> resolved
status: open -&g
New submission from Daniel Alley :
Disclaimer: I'm not familiar with the interpreter internals, nor am I really a
C dev, so I could be misinterpreting these results due to inexperience.
I've been attempting to debug a memory leak which I thought was caused by a C
API extension t
Daniel Alley added the comment:
This seems likely to be a duplicate of https://bugs.python.org/issue41588, as
run_in_executor(None, ...) submits tasks to a ThreadPoolExecutor underneath the
hood.
--
nosy: +dralley
___
Python tracker
<ht
