Re: Error when compiling a large file

[Miguel Jesus]

James,
 
I couldn't get it to compile even when I try to compile th whole score.
 
That means the problem is on my side. I have to check the jEdit definitions to 
see if there is something going wrong. Do you (or anyone else) have any ideas 
on what might cause this problem? I tried to run it as an admin in case windows 
was being funny just because of that but it didn't solve it.
 
Once again, thanks for the reply!
 
Miguel
 

________________________________
 From: James <address@hidden>
To: Miguel Jesus <address@hidden> 
Cc: Bug-Lilypond <address@hidden> 
Sent: Tuesday, 19 February 2013, 9:36
Subject: Re: Error when compiling a large file
  

Miguel,

Keeping the group on the email thread.


On 19 February 2013 03:02, Miguel Jesus <address@hidden> wrote:

James,
>  
>I can't tell at what point the file stopped to compile because I've been using 
>several versions of lilypond since I started writing this file. When I started 
>I was using 2.14.2 or something like that. All I can tell you is that if I use 
> 
>showLastLength = R1*800
> 
>it doesn't compile but with
> 
>showLastLength = R1*700  
> 
>it does.
> 
>This has happened before but it was corrected, I just don't remember which 
>version it was. At that point I was probably at bar 1000 or close to it.
> 
>Some of the instruments have more bars than others because I'm copying things 
>but that has never caused a problem before and I guess it shouldn't. 
> 
>My computer is an Intel QuadCore Q6600 @ 2,40GHz, 4Gb Ram running Windows 
>Vista Home Basic 64-bit. I'm using jEdit as well.
> 
>By the way, thanks for the quick reply! 
> 
>Miguel


I did get the file to compile - it did take a few minutes (my own compositions 
are 150 bars at the most so nothing like this) 

--snip--
address@hidden:~/Desktop$ time lilypond m\ orchestral\ score.ly
GNU LilyPond 2.16.2
Processing `m orchestral score.ly' 
Parsing...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320][328][336][344][352][360][368][376][384][392][400][408][416][424][432][440][448][456][464][472][480][488][496][504][512][520][528][536][544][552][560][568][576][584][592][600][608][616][624][632][640][648][656][664][672][680][688][696][704][712][720][728][736][744][752][760][768][776][784][792][800][808][816][824][832][840][848][856][864][872][880][888][896][904][912][920][928][936][944][952][960][968][976][984][992][1000][1008][1016][1024][1032][1040][1048][1056][1064][1072][1080][1088][1096][1104][1112][1120][1128][1136][1144][1152][1160][1168][1176][1184][1192][1192]
 
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 92 or 93 pages...
Drawing systems...
Layout output to `m orchestral score.ps'... 
Converting to `./m orchestral score.pdf'...
Success: compilation successfully completed

real3m8.987s
user2m56.431s 
sys0m11.789s

--snip--

I have a quite powerful desktop and use Linux, but I only saw 1 CPU being used 
and never above 2.5GB of RAM (using the 'top' command - a bit like Windows' 
Task Manager/Processes if you haven't used top before). 

So is it only when you use 'showLastLength' that you get the problem or even 
when you try to compile the whole score?

I commented out the showLastLength line in your file and while I got a load of 
'unterminated tie' and unexpected tempo change errors - expected when using 
this command - it does compile with no problems 

--snip-
lots of warnings..
.....

m orchestral score.ly:15551:12: warning: unterminated tie
<la  
            dos mi>4\arpeggio r r2 |
m orchestral score.ly:15551:9: warning: unterminated tie
<
         la dos mi>4\arpeggio r r2 | 
[296][304][312][320][328][336][344][352][360][368][376][384][392][400][408][416][424][432][440][448][456][464][472][480][488][496][504][512][520][528][536][544][552][560][568][576][584][592][600][608][616][624][632][640][648][656][664][672][680][688][696][704][712][720]
 
m orchestral score.ly:16540:8: warning: unterminated tie
        mi,8^\smpf si'16 do si8 la |
[728]
m orchestral score.ly:17260:8: warning: unterminated tie 
        mi,8^\smpf si'16 do si8 la |
[736][744][752][760][768][776][784][792][800][808][816][824][832][840][848][856][864][872][880][888][896][904][912][920][928][936][944][952][960][968][976][984]
 
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 71 or 72 pages...
Drawing systems...
Layout output to `m orchestral score.ps'... 
Converting to `./m orchestral score.pdf'...
Success: compilation successfully completed

real2m21.146s
user2m11.020s 
sys0m9.565s

--snip-

Again I didn't notice much more usage in the RAM or CPU than before.

I know that that probably doesn't help that much. I do have a windows machine I 
could try it on, but that wil have to wait for now as I have to get to work!

I've attached your Zip file here in case anyone else with Windows wants to give 
it a go. 

James



> 
> From: James <address@hidden>
>To: Miguel Jesus <address@hidden> 
>Cc: address@hidden 
>Sent: Monday, 18 February 2013, 20:43
>Subject: Re: Error when compiling a large file
> 
>
>
>MIguel,
>
>
>On 18 February 2013 02:27, Miguel Jesus <address@hidden> wrote:
>
>> I'm not top posting.
>>
>>I'm trying to compile a large file with lilypond 2.16.2 (about 1200 bars) but
>>I keep getting an error:
>>
>>"This application has requested the Runtime to terminate it in an unusual way.
>>Please contact the application's support team for more information."
>>
>>I also got a st9bad_alloc error with 2.17.2 and 2.16.0
>>
>>
>
>
>Is there a point where the file does compile? That is, i doubt you just 
>created 1200 bars without compiling at some point, so am wondering where the 
>'point' that the compilation started to fail, was after you set bar 1199 for 
>instance or when you put in that last accidental or perhaps when you added 
>that second voice etc. 
>
>
>Also if you have a link or a zipped .ly file I can try to see what happens on 
>my server when I compile it.
>
>
>What is the spec of your computer you are compiling it under as that may also 
>be telling. 
>
>
>James
>
>
>