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 -> closed
__
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 that we are usi
