Blind leading the blind: Chase the memory leak about braindump HOT 9 CLOSED

Some possible tools to throw into the discussion if time allows:

• https://github.com/fabianp/memory_profiler
• https://github.com/joerick/pyinstrument
• https://github.com/rkern/line_profiler

Would love a session on profiling mixed C/python code, though! I tend to do the simplest thing of building quick-and-dirty Cython wrappers in a notebook and using the %%time cell magic. But there must be better tools out there that leverage C profiling tools. Might be a separate topic you could add if we don't get to it for this one, @drdavella?

from braindump.

Maybe this would be a good opportunity to talk about tools for C analysis and instrumentation like valgrind and various sanitizers? And maybe gdb?

from braindump.

I assume this would let me learn more about profilers? If so, you have my vote.

from braindump.

If you demo gdb make sure you have https://github.com/gdbinit/Gdbinit installed.
Everyone will "oooo" and "ahhh".

from braindump.

@drdavella -- Using valgrind with Python does not seem to be straightforward (see https://code.google.com/archive/p/distnumpy/wikis/valgrind.wiki). If you have any tips on this, let us know!

from braindump.

No, I don't have a lot of experience with that, just with pure C code. I wasn't sure whether Spec2Pipeline was pure C or Python extension code. I could look into this kind of thing more though.

from braindump.

Spec2Pipeline is pure python.

from braindump.

Yikes!

from braindump.

Thought we did that.

from braindump.