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?
--
Julien
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
