[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond taking forever to typeset
From: |
Mojca Miklavec |
Subject: |
Re: Lilypond taking forever to typeset |
Date: |
Tue, 12 Jul 2016 13:06:28 +0200 |
On 12 July 2016 at 11:33, Masamichi Hosoda wrote:
>>> 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
>
> If you use the binary which is downloaded from LilyPond website,
> fontconfig cache directory is `~/.lilypond-fonts.cache-2`.
> So you can delete the cache by the following command.
>
> $ rm -fr ~/.lilypond-fonts.cache-2
Wonderful, thank you very much the hint, this did the trick.
So here it goes ...
(gdb) r test.ly
Starting program:
/Applications/LilyPond.app/Contents/Resources/bin/lilypond test.ly
warning: Tried to remove a non-existent library: /usr/lib/libstdc++.6.0.9.dylib
warning: Tried to remove a non-existent library: /usr/lib/libstdc++.6.0.9.dylib
...
warning: Tried to remove a non-existent library: /usr/lib/libstdc++.6.0.9.dylib
Reading symbols for shared libraries
+++++++++..+...........................................................................................................................................
done
Reading symbols for shared libraries . done
GNU LilyPond 2.19.45
Reading symbols for shared libraries . done
^C
Program received signal SIGINT, Interrupt.
0x988f6e38 in memmove$VARIANT$sse3x ()
(gdb) backtrace
#0 0x988f6e38 in memmove$VARIANT$sse3x ()
#1 0x00b54b8f in cf2_glyphpath_moveTo ()
Previous frame inner to this frame (gdb could not unwind past this frame)
second attempt:
^C
Program received signal SIGINT, Interrupt.
0x99885a62 in read$NOCANCEL$UNIX2003 ()
(gdb) backtrace
#0 0x99885a62 in read$NOCANCEL$UNIX2003 ()
#1 0x9891aee6 in __sread ()
#2 0x9891af0e in _sread ()
#3 0x9891b465 in __srefill1 ()
#4 0x9891bece in _fseeko ()
#5 0x9891b9a2 in fseek ()
Let me know if there is anything else I could try or if I should
collect more "statistics".
This time the first lilypond run took 2,5 minutes to complete
(apparently I had additional problems with swap yesterday that
prolonged the process to almost 10 minutes).
Mojca
- Re: Lilypond taking forever to typeset, (continued)
- Re: Lilypond taking forever to typeset, Werner LEMBERG, 2016/07/11
- Re: Lilypond taking forever to typeset, David Kastrup, 2016/07/11
- Re: Lilypond taking forever to typeset, Mojca Miklavec, 2016/07/11
- Re: Lilypond taking forever to typeset, Masamichi Hosoda, 2016/07/12
- Re: Lilypond taking forever to typeset,
Mojca Miklavec <=
- Re: Lilypond taking forever to typeset, David Kastrup, 2016/07/12
- Re: Lilypond taking forever to typeset, Mojca Miklavec, 2016/07/12
- Re: Lilypond taking forever to typeset, David Kastrup, 2016/07/12
- Re: Lilypond taking forever to typeset, Werner LEMBERG, 2016/07/12
- Re: Lilypond taking forever to typeset, Mojca Miklavec, 2016/07/13
- Re: Lilypond taking forever to typeset, Werner LEMBERG, 2016/07/13
- Re: Lilypond taking forever to typeset, Mojca Miklavec, 2016/07/13
- Re: Lilypond taking forever to typeset, Masamichi Hosoda, 2016/07/13
- Re: Lilypond taking forever to typeset, Mojca Miklavec, 2016/07/14
- Re: Lilypond taking forever to typeset, David Kastrup, 2016/07/15