On Nov 14, 2011, at 3:58 PM, m...@apollinemike.com wrote: > Some more info. > With the most recent patch set, when I comment out the footnote engraver and > the grob array callbacks for system, the segfault still happens. > So it is likely coming from something I'm stashing in probs. I'll try to > figure out what it is... > > Cheers, > MS
So I figured it out. The two grob arrays were not declared in any interface, nor were they documented. I fixed this and now there's no memory leak. This may be a valuable piece of information for future research on memory leaks in LilyPond. For whatever reason, when a property is looked up and/or passed around and does not belong to an interface nor is documented, LilyPond will compile clean but leak memory. Of course, it'd be great if during the compilation stage some tool could do a scan for all get/set property/object calls in LilyPond (in .ly, .scm, and .cc documents) and crash the compilation if called properties lack interfaces and/or docstrings. This seems like a separate (and less pressing) issue from the memleak, however. Cheers, MS _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
