bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make doc problem


From: Phil Holmes
Subject: Re: make doc problem
Date: Fri, 27 Jan 2012 13:38:26 -0000

----- Original Message ----- From: "Julien Rioux" <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Thursday, January 26, 2012 11:00 PM
Subject: Re: make doc problem


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


I'm trying to look at memory usage on my Ubuntu box. If I watch the build using System Monitor, I rarely see more than a gig used. However, using "free" even my dormant machine is now showing 3 Gigs used. Is this because I have around 2 Gigs marked as "cache"? Is the actual in-use memory used-cache?

--
Phil Holmes





reply via email to

[Prev in Thread] Current Thread [Next in Thread]