Re: [Fwd: memory leaks in python interface [was Hash view questions]]

> >> Your sample code does show increasing memory use on my setup as  
> >> well.  Is there a way to find out what the content or at least sizes/ 
> >> counts of the leaked memory areas is in Python?
> > 
> > Yes!  A beautiful tool known as valgrind [1].  It tells me that you are right
> > and the C++ metakit code is exonerated.
> > 
> > This is because the stack traces of the code that allocated the leaking memory
> > do not have any metakit functions in them.  Hm... the biggest one has
> > posix_read() in it.  The other two are both involving allocation of Python
> > Ints...

Concerns with the Python interface yesterday prompted me to open
this folder in my mail client for the first time in at least a month.

This was the first thread I saw.

I think the Python interface needs to be rewritten. Gordon McMillan's
tools and sites have been offline for years now it seems. I don't
know to what extent he and JCW collaborated for the Python interface,
but I do know the Python interface needs work/re-work.

It may be irrelevant that Gordon seems to have disappeared and
that the Python wrappers use his SCXX Python/C++ wrapping tool.

At the very least someone should choose to switch to SWIG.
At most, someone should simply write the wrapper "by hand".

-- 
 kai
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit