Dirk Lattermann <> writes:
> Hi!
>
> Is it really true that lilypond now (1.3.40) uses much more
> memory than the old 1.2 versions did? several of my scores I
> cannot translate into tex any longer (on my machine, 32MB),
> because when preprocessing elements and at output, lilypond is
> swapping and swapping. Earlier 1.3 versions were worse, though,
> until the changelog said 'many memory holes fixed' or so.
> I wonder if there are some holes left. Like this, lilypond is
> nearly unusable to me :-(( . I don't want to wait >3 hours for the
> processing of a piano score (even if there's much music in it).
> With lily 1.2.17, it was done in ~20min, if I recall right.
I don't think that there are many holes left, I plugged them all a few
patchlevels ago. The memory usage is caused by GUILE integration, I
think. And maybe the GUILE integration fragments memory more, giving
worse swapping behavior.
There is little I can do to alleviate this, going back to the old code
(which was very bug-prone) is not an option. Perhaps you can buy some memory?
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
