Re: strange error causes Lilypond refuse to compile

[Graham Percival]

(for your other email)
I would attempt to isolate and fix these problems before playing
with virtual memory.


I must admit that the error message looks like a problem with
memory allocation, but I think the solution to this lies in either
your tweaks, or in a bug with 2.11.49.  Unfortunately, tracking
down the cause will likely not be easy.

I took a quick look at your files, and I couldn't see anything
obviously wrong -- you've done a good job of separating your
tweaks from your music definition.  I can think of a few
possibilities:
- lilypond has trouble with your tweaks (I'm testing
  MarkLine right now, but commenting that out doesn't stop the
  problems)
- lilypond has trouble dealing with large paper sizes.  (nope, not
  this; commenting out the paper line doesn't fix it)
- maybe it's the number of StaffGroup nestings?  What happens if
  you comment out a bunch of lines in your -score file and have
everything inside a single GrandStaff or StaffGroup?
- maybe one or your tweaks happens to require a lot of CPU power
  to calculate?  What if you remove all your tweaks?  (ie in your
defs, change all the definitions to be
  blah = {
%
%
%
}

- if you try compiling your score with certain instruments removed
  (ie comment out all the winds, then percussion, then strings,
etc), does the problem go away?


Sorry I can't help more; I've tried a few things without any
change, but I can't spend more time on it.
- Graham

On Sun, 22 Jun 2008 14:03:13 +0800 (CST)
hhpmusic <address@hidden> wrote:

> Hello,
>   I'm again trapped in my symphony for the earthquake. I finished the
> introduction and now come to the first theme. Before writing the
> first theme, the score was compiled well. But now, only after 8 bars,
> the score can't be compiled any more. The log file shows the
> following strange error: Parsing...terminate called after throwing an
> instance of 'std::bad_alloc' what():  St9bad_alloc Then a warning
> window comes up, but my screen reader can't read it. What's wrong
> with my score? Is the problem only because of my machine? Sincerely
> Haipeng 
>