On 2012-01-27 00:00, Julien Rioux wrote:
On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.
Cheers,
Reinhold
Is it a bug? We're talking about lilypond running with the
-dread-input-files flag here. Once a snippet has been processed and
lilypond moves on to the next one, there is no reason to hold onto the
memory used by the previous snippet, right?
Please check the -devel mailing list (e.g. thread "Memleaks or not" last
August/September), where I already observed this. I fully agree that
after one file is processed, lilypond should reset to its initial state
and not need more memory than before.
I have no idea why the memory is going up like it does. To me it doesn't
look like a classical memleak, but rather somthing with the Guile
garbage collection...
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial& Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
