Re: Error when compiling a large file

[James]

Hello,

On 19 February 2013 10:06, Phil Holmes <address@hidden> wrote:

> "James" <address@hidden> wrote in message news:CA+T3wFm6ocUSfVyd=**
> address@hidden
> Miguel,
>
>
>  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).
>>
>
> Single core is correct - LilyPond is single threaded.
>
>
>  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.
>>
>
> Just run is on my normal desktop - 6 Gig RAM, Vista 64 bit.  It dies after
> 6 minutes, having consumed 1.3 Gigs of RAM.  I suspect it might be a
> problem with Windows memory allocation - it's possible each process is
> restricted to how much RAM it can allocate.
>

Yes there is a limit per process - the software company I work for hits
that all the time so we have to spawn multiple instances of a particular
process to get the RAM we need to use for a given driver. Slightly
different to what LP does but there are limits.

However these are not normally something that you will hit as a general
user on 64 bit OSs.

I have just run it on my Win7 32bit 2G RAM and get this

--snip--
C:\Users\jlowe.DCSW\Desktop>lilypond "m orchestral score.ly"
GNU LilyPond 2.16.1
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][1
84][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320][328][336][344][352][360][368][3
76][384][392][400][408][416][424][432][440][448][456][464][472][480][488][496][504][512][520][528][536][544][552][560][5
68][576][584][592][600][608][616][624][632][640][648][656][664][672][680][688][696][704][712][720][728][736][744][752][7
60][768][776][784][792][800][808][816][824][832][840][848][856][864][872][880][888][896][904][912][920][928][936][944][9
52][960][968][976][984][992][1000][1008][1016][1024][1032][1040][1048][1056][1064][1072][1080][1088][1096][1104][1112][1
120][1128][1136][1144][1152][1160][1168][1176][1184][1192][1192]
Preprocessing graphical objects...terminate called after throwing an
instance of 'std::bad_alloc'
  what():  St9bad_alloc

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.

--snip--

Which is what the user is getting.

I watched the Process Monitor slowly use up all the 1.2GB of Free memory I
have on this relatively underpowered desktop get all used up when it then
borks.

So I think the user is running out of memory for this file.

The event logs shows

--snip--

Faulting application name: lilypond.exe, version: 2.16.1.1, time stamp:
0x509d1610
Faulting module name: lilypond.exe, version: 2.16.1.1, time stamp:
0x509d1610
Exception code: 0x40000015
Fault offset: 0x004237ce
Faulting process id: 0xed8
Faulting application start time: 0x01ce0e9c4bdffa41
Faulting application path: C:\Program Files\LilyPond\usr\bin\lilypond.exe
Faulting module path: C:\Program Files\LilyPond\usr\bin\lilypond.exe
Report Id: 6379eb11-7a90-11e2-8407-001d09802a5d

--snip--

Now looking in ntstatus.h the exception code just gives me

STATUS_FATAL_APP_EXIT?

Which is just a generic error message - nothing more.

Doing a quick google for 'what():  St9bad_alloc' it seems that this is
likely to be because we are running out of memory.

The question is how we can reduce the memory usage I guess but that is
certainly beyond my pay grade.

HTH

James