On Mon, Oct 3, 2016 at 3:38 PM, Trevor Bača <trevorb...@gmail.com> wrote:
> > > On Wed, Sep 14, 2016 at 3:26 PM, Carl Sorensen <c_soren...@byu.edu> wrote: > >> More information (this is under OSX 10.8.5 Mountain Lion): >> >> >> On 9/14/16 9:16 AM, "lilypond-devel on behalf of Trevor Bača" <lilypond- >> <mailto:lilypond-devel-bounces+c_sorensen=byu....@gnu.org> >> >> >7. LilyPond versions 2.19.47 and 48 are "unhealthy": these two most >> recent >> >versions of LilyPond appear to rebuild the font cache on *EVERY* run of >> >LilyPond, meaning that every run of LilyPond takes 40 seconds or more. >> >> >> On OSX 10.8.5 Mountain Lion, command line runs are all fast. The first >> one after downloading 2.19.48 was slow, but no others. >> >> I wonder if the new security stuff on El Capitan is changing the >> owner/group of the font cache files, and that is giving problems. >> >> Has anyone done an ls -l ~/lilypond-font-cache-2 to see if the owner, >> group, and permissions are right? >> > > > With LilyPond 2.19.46 (last healthy build under OSX 10.11 / 10.12): > > $ ls -l ~/.lilypond-fonts.cache-2 > total 2272 > -rw-r--r-- 1 trevorbaca staff 617944 Oct 3 15:14 > 84c0f976e30e948e99073af70f4ae876-i686-apple-darwin8.cache-7 > -rw-r--r-- 1 trevorbaca staff 518000 Oct 3 15:15 > b0a71e6bf6a8a1a908413a823d76e21f-i686-apple-darwin8.cache-7 > -rw-r--r-- 1 trevorbaca staff 23944 Sep 14 10:19 > ce2f012eabd1de3f1e401def0f51e425-i686-apple-darwin8.cache-7 > > > With LilyPond 2.19.48 ("unhealthy" build under OSX 10.11 / 10.12) : > > $ ls -l ~/.lilypond-fonts.cache-2 > total 2272 > -rw-r--r-- 1 trevorbaca staff 617944 Oct 3 15:14 > 84c0f976e30e948e99073af70f4ae876-i686-apple-darwin8.cache-7 > -rw-r--r-- 1 trevorbaca staff 518000 Oct 3 15:31 > b0a71e6bf6a8a1a908413a823d76e21f-i686-apple-darwin8.cache-7 > -rw-r--r-- 1 trevorbaca staff 23944 Oct 3 15:31 > ce2f012eabd1de3f1e401def0f51e425-i686-apple-darwin8.cache-7 > > > So permissions and ownership settings appear to be the same between > 2.19.46 and 2.19.48 under OSX 10.11 (and 10.12). > > Note that LilyPond versions up to (and including) 2.19.46 work fine under > 10.11; it's only versions 2.19.47 and .48 that exhibit the problem. (I.e., > seems unrelated to OSX version and definitely related to the two most > recent LilyPond builds.) > Important CLUE: It's definitely the case that LilyPond 2.19.47 and .48 are rebuilding (one of three) font caches at every run. The phenomenon is testable by reading the last modification time in the output of `ls` after successive LilyPond runs. EXAMPLE: $ lilypond test.ly < snip > $ ls -l ~/.lilypond-fonts.cache-2 total 2272 -rw-r--r-- 1 trevorbaca staff 617944 Oct 3 15:14 84c0f976e30e948e99073af70f4ae876-i686-apple-darwin8.cache-7 -rw-r--r-- 1 trevorbaca staff 518000 Oct 3 15:36 b0a71e6bf6a8a1a908413a823d76e21f-i686-apple-darwin8.cache-7 -rw-r--r-- 1 trevorbaca staff 23944 Oct 3 15:31 ce2f012eabd1de3f1e401def0f51e425-i686-apple-darwin8.cache-7 $ lilypond test.ly < snip > $ ls -l ~/.lilypond-fonts.cache-2 total 2272 -rw-r--r-- 1 trevorbaca staff 617944 Oct 3 15:14 84c0f976e30e948e99073af70f4ae876-i686-apple-darwin8.cache-7 -rw-r--r-- 1 trevorbaca staff 518000 Oct 3 15:40 b0a71e6bf6a8a1a908413a823d76e21f-i686-apple-darwin8.cache-7 -rw-r--r-- 1 trevorbaca staff 23944 Oct 3 15:31 ce2f012eabd1de3f1e401def0f51e425-i686-apple-darwin8.cache-7 I ran LilyPond 2.19.48 twice, with 4 minutes between runs. Notice the lines highlighted in cyan: Time of last modification of the second of the three caches in ~/.lilypond-fonts.cache-2 increments from 15:36 to 15:40. Meaning that LilyPond 2.19.48 is definitely rebuilding a font cache prior to each run. -- Trevor Bača www.trevorbaca.com soundcloud.com/trevorbaca _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
