Re: Lilypond taking forever to typeset

[David Kastrup]

Werner LEMBERG <address@hidden> writes:

>> I'm unable to provide a minimum example. I'm 99% sure that the long
>> delay is independent of the input.
>
> OK.
>
>>> Do you have time to bisect the problem?
>> 
>> Do you happen to have an archive of OS X binaries?
>
> Sorry, I don't know.
>
>> I could do some testing with MacPorts (I could easily compile from
>> source, I only have to invest the initial time to compile all the
>> dependencies), but I'm afraid that it might not be reproducible
>> there because there might be a single fontconfig database for the
>> whole MacPorts installation.
>
> Actually, this is what makes most sense to me.  Maybe MacPorts
> provides older binaries?

Also it might be interesting where it happens.  Perhaps run it under a
debugger, give it a C-c during its long delay and then take a look at
the resulting backtrace to see where LilyPond is when the delay happens?
I suspect that the long delay is spent completely in some library call
without intermediate return to LilyPond, so it would be good to know
just which call.

Wait, didn't we have some experimentation with font name _patterns_
recently in order to reliably find some fonts?  Maybe the use of font
name patterns triggers a fontname database rebuild?

-- 
David Kastrup