On Nov 14, 2011, at 12:43 PM, d...@gnu.org wrote:
> lily/grobarray.cc contains the following:
>
> SCM
> Grob_array::mark_smob (SCM s)
> {
> (void) s;
>
> #if 0 /* see System::derived_mark () const */
> Grob_array *ga = unsmob_grob_array (s);
> for (vsize i = 0; i < ga->grobs_.size (); i++)
> scm_gc_mark (ga->grobs_[i]->self_scm ());
> #endif
> return SCM_UNDEFINED;
> }
>
> Consequently, elements of a grob array are not protected from garbage
> collection when no other references to the grobs remain.
>
> This is rather the reverse of a memory leak, however.
>
Agreed.
Reinhold - how did you do the memory profiling on all of the regtests? I can
figure out how to do it for a single file, but not the regtests in succession.
This'd help me figure out where/why lilypond is fizzling out.
Cheers,
MS
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
