On Nov 14, 2011, at 12:05 PM, pkx1...@gmail.com wrote:
> Passes make but fails make check see:
>
> http://code.google.com/p/lilypond/issues/detail?id=1791#c13
>
> James
>
> http://codereview.appspot.com/4877041/
Thanks James.
As I feared, the memleak is still there.
I've combed the code several times but cannot find where it's leaky. It's of
course possible that the leak is not caused by the code per se but rather
another structure in LilyPond that I'm using incorrectly (or that has a bug).
The valgrind backtrace isn't showing any memory leaks (meaning nothing beyond
the use of `new' in several functions in grob.cc, but these come up all over).
The only semi-fancy memory things I'm doing are the use of an array in
grob_2D_less and the creation/modification of grob arrays. But I don't think
that either of these are done fishily. Does anyone have any intuition in
reading over the code as to places where memory may be sapped?
Cheers,
MS
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
