On 11 July 2016 at 15:27, David Kastrup wrote: > Werner LEMBERG 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?
The main problem is: I need an idea of where to start looking for the font cache (or repeat the experiment on a clean machine). Unless I delete the cache, I'm unable to reproduce the problem. If I just switch from 2.18 to 2.19 or if I delete 2.19 and install it again from scratch, I'm not able to reproduce the behaviour, so the font cache is obviously not in the folder with LilyPond.app. For all I know: - I tried to run some version of Lilypond last week, it "hanged" a number of times. It was from 2014, but I deleted it and decided to reinstall Lilypond 2.18. That one seems to be from 2014 as well (it could be the same version), but it worked out of the box. - Today I downloaded 2.19 from your website and it experienced the same symptoms, but I did an investigation before deleting the program and found that font cycling. Mojca _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
