Re: [Lilypond-auto] Issue 3194 in lilypond: crash when too manybars requested

[Trevor Daniels]

> Comment #7 on issue 3194 by address@hidden: crash when too many  
> bars requested
> http://code.google.com/p/lilypond/issues/detail?id=3194
> 
> Sorry, Trevor, it's not that.  My physical memory is 6 Gigs, and I've  
> written an app that repeatedly allocates memory and ended up with over 5  
> gigs, at which point I took pity on the other applications and killed it.   
> With the test file Liylpond gets to just over 1 gig and then dies.  So it's  
> not a lack of actual available memory, it's more complex than that.  But I  
> don't know what/why.

I think you're right.  I tried restricting the physical memory used by Guile
with LILYPOND_GC_YIELD, which did reduce the working-set size,
but made no difference to the LP failure.  The tests did wreck the paging
system though - around 50% of the pages normally available in physical 
memory were not returned to the free chain when the applications ended.
After that the system was paging so heavily it was unusable and had to be 
rebooted.

Having spent two days on this I'm reluctant to spend more time running
these very time-consuming and stressful tests.  Keeping my little laptop
disk seeking continuously can't be good for it.

Trevor