[Top][All Lists]

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

Re: Lilypond slow to start up on the Mac

From: Tim McNamara
Subject: Re: Lilypond slow to start up on the Mac
Date: Mon, 23 Apr 2018 11:22:50 -0500

> On Apr 23, 2018, at 10:40 AM, Arle Lommel <address@hidden> wrote:
> I’ve noticed on the Mac for some time that the first time I invoke Lilypond 
> from an external application after a reboot, it can take quite a while for it 
> to respond. Normally this is something like a 40–60 second delay, after which 
> Lilypond behaves normally. But a few days ago, after I updated to OS X 
> 10.13.4, it seemed that Lilypond was totally unresponsive over much longer 
> periods. After waiting about ten minutes, I finally walked away for dinner, 
> and when I came back, it was working normally. This happened with the latest 
> development build, but I’ve also had delays with the stable build (although 
> never as long as this was).
> I was invoking Lilypond through Frescobaldi, but I’ve had the same (shorter) 
> initial delays on JEdit, and on multiple machines in the past.
> During this longer wait, I could launch and initiate a 
> typesetting activity from within it with no problem, so it is not Lilypond 
> itself that seems to be the problem, but rather something specific to 
> external applications calling it.
> Is this a known issue? If so, any ideas on ways to fix it other than 
> typesetting something and walking away for 20 minutes before it responds?

I have also seen this on several prior versions of the Mac OS as well.  I am 
invoking Lilypond via Frescobaldi, so I don’t know if there is something with 
how the OS handles those requests or if the OS is just slow to launch Lilypond 
(I haven’t tested it from the command line in Terminal).  Once it’s been 
launched once, subsequent invocations are immediate.  I do not recall if this 
only happened after a reboot, my sense is that I see it somewhat randomly even 
without a reboot.

I don’t know if there would be anything helpful in any of the logs that might 
be explanatory.

reply via email to

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