Joe Neeman wrote:
On Fri, 16 Nov 2007 18:18:50 David Bobroff wrote:
I had a strange exit from a LilyPond run. I've never seen this before.
I was running a collection of nearly 70 etudes. It appeared to be
running just fine. I got lots of "Preprocessing..." and
"Interpreting..." etc. and then when it got to "Fitting music on 86 or87
pages..." it didn't progress any further for a long time. I let it run
overnight to see if Lily just needed more time to think about it. When
I got up in the morning I found this:
As Hans said, the error means that you ran out of memory. Does it help if you
use the minimal page-breaking algorithm as described in section 11.4.5 of the
manual?
Joe
Uh..yuh. That did it. Thanks! After Hans commented about memory I
tried running my file again with the Task Manager open showing
performance stats. When LilyPond got to the page calculation and didn't
progress further I saw the Page File Usage climb steadily upwards. This
box has 2Gb of physical RAM and I shut down Lily when it got up to about
1.93Gb of usage. Then I used your suggestion about minimal page
breaking and not only did it work but it cut down the processing time to
under three minutes.
-David
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
