bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lilypond crash


From: Phil Holmes
Subject: Re: Lilypond crash
Date: Wed, 6 Oct 2010 16:58:22 +0100

"Valentin Villenave" <address@hidden> wrote in message news:address@hidden
On Tue, Oct 5, 2010 at 11:25 PM, Phil Holmes <address@hidden> wrote:
The other issue is - all these test cases with multiple repeats are
artificial - the real question is - does it do long _real_ scores?

I always had the feeling (though nothing to document it) that LilyPond
is much better at compiling real-world scores, no matter how huge,
than {\repeat unfold 10000} stressing tests. I've had no problem (on
GNU/Linux, that is) building either my or Nicolas' scores. Perhaps the
memory handling/garbage collection is better with real-world scores?
(e.g. with barchecks, music variables, different contexts being used,
etc?)

Similarly, here's what Han-Wen once told me when I tried compiling a
huge score imported with midi2ly:
http://lists.gnu.org/archive/html/lilypond-user/2006-10/msg00339.html

" A dirty midi file won't have note-ends aligned with barlines, which
means that the entire score will end up in one huge line without
breaks. This will undoubtedly stretch lilypond performance in
unexpected ways."

Cheers,
Valentin

I mentioned before that I'm slowly compiling a full Mikado score, which will be about 150 pages long. It's currently 78 pages. It takes a while to compile, but allocates lots more memory than I was using with the repeat unfold stuff that crashed.

--
Phil Holmes
Bug Squad






reply via email to

[Prev in Thread] Current Thread [Next in Thread]