Re: *** buffer overflow detected ***: [...]/bin/lilypond terminated

[David Kastrup]

Knut Petersen <address@hidden> writes:

> If lilypond master is spawned from a lualatex 1.0.4 process with 1023 open 
> files it hits a hard limit:
>
>    lilypond -E --pdf -O TeX-GS -daux-files=\#t -dgs-load-fonts=\#t tmplily.ly
>
> then fails with
>
>     >>tmplily.ly<< wird verarbeitet
>    Analysieren...
>    Interpretation der Musik...[8][16][24]
>    Vorverarbeitung der grafischen Elemente...
>    Ideale Seitenanzahl wird gefunden...
>    Musik wird auf 7 oder 8 Seiten angepasst...
>    Systeme erstellen...
>    Layout nach >>tmplily.eps<< ausgeben...
>    Konvertierung nach >>tmplily.pdf<<...
>    *** buffer overflow detected ***: [...]/bin/lilypond terminated

Sounds like the problem in this particular case happens when calling
Ghostscript.  I am not sure that LilyPond could do anything about that.
Of course, I am also not sure that LilyPond will behave well when
running out of file handles itself: running out of resources is a
possibility that programmers love to ignore.

>
> The nofile soft limit is 2048, gcc (SUSE Linux) 7.2.1 20171020 [gcc-7-branch 
> revision 253932] is used.
>
> Part of the problem is that lualatex keeps all pdf files that are include via 
> \includegraphics open, so reaching 1023 open files is possible.
> xelatex behaves differently - it does not keep files included by 
> \includegraphics open.

That sounds like something that would be worth reporting to the LuaTeX
developers.

-- 
David Kastrup