Re: Error when compiling a large file

[Phil Holmes]

"David Kastrup" <address@hidden> wrote in message 
news:address@hidden
> "Phil Holmes" <address@hidden> writes:
>
> > "James" <address@hidden> wrote in message
> > news: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.
>
> It's not a "problem with Windows memory allocation": 1.3 Gig is already
> totally ridiculous for that kind of file.
>
> In fact, I'd probably reduce the allowed allocation artificially for
> testing this problem in order to save time.
>
> --
> David Kastrup

Lilypond has always used a lot of memory.  If I run the test file Eluze 
created on 2.12 it goes up to just shy of a gig.  I'd assume there are minor 
variations in the amount of memory the various layout systems use, and 2.12 
was just too little to cause memory to be allocated, and subsequent 2.13 
versions just too much.

--
Phil Holmes
Bug Squad