On Wed, Jul 14, 2010 at 3:34 PM, Arno Waschk <address@hidden> wrote:
On Wed, 14 Jul 2010 21:21:28 +0200, Joe Neeman <address@hidden>
wrote:
On Wed, Jul 14, 2010 at 9:49 AM, Arno Waschk <address@hidden> wrote:
seems this is something which is new (i tried as well 2.13.26).
it just meens that the swap partition is full...
looks my score is too long for lilypond, or too many accidentals?
the following:
\version "2.13.28"
\layout { ragged-right = ##t }
\relative c' {
\key a \major
\repeat unfold 1000 {
f8 g f g fis gis a a
f8 g f g fis gis a a
%\pageBreak
f8 g f g fis gis a a
f8 g f g fis gis a a}
c r r4 r2
}
dies in Accidental_placement::get_relevant_accidentals
where etls.size is reported as 16000 in the loop. On my machine at
i~13000,
4 GB memory, 2 GB swap space...
I just fixed a bug which caused memory consumption and time that is
quadratic in the number of accidentals, so this example should work
much
better now.
Wow! First impression is huge running time reduction. Rough guess 80%
for
my large score. So 400% performance gain...
But in the end it dies again with that memory error, but i wll check for
that.
Is this with git master or with my patch for extra caching?
In my little example it dies differently, obviously an endless loop in
grob-smob.cc:50 according to an endless backtrace in gdb.
This is also a memory problem, since grob-smob.cc:50 is run as part of
guile's garbage collections.
I have uploaded my patch for comments here:
http://codereview.appspot.com/1817045
Cheers,
Joe