warning (hpack filter): stack overflow

• Auswertung: henribranken
• Verantwortlicher: h7k
• Typ: Fehler
• Status: Geschlossen
• Komponente: (Keine)
• Meilenstein: (Keine)
• Priorität: 7
• Schweregrad: 7
• Lösung: Gefixt
• Datei: Keine

Details Antworten

Please have a look at the following post: https://tex.stackexchange.com/questions/652379/warning-hpack-filter-error-xmf-dist-tex-luatex-luaotfload-fontloader-20-2

Ticket-Verlauf (3/7 Historien)

2022-08-02 20:08 Aktualisiert von: henribranken

• New Ticket "warning (hpack filter): stack overflow" created

2022-08-02 20:18 Aktualisiert von: h7k

• Verantwortlicher Update from (Keine) to h7k
• Typ Update from Supportanfragen to Fehler

Kommentar Antworten

Sorry, I didn't notice that. LuaTeX-ja seems to have a memory leak. I'll check that.

2022-08-02 20:43 Aktualisiert von: h7k

Kommentar Antworten

Smaller example:

 %#! luatex
 \loggingall
 \input luatexja.sty
 \def\A{\advance\count0 1\shipout\vbox{\vrule}\A}\A

2022-08-04 18:47 Aktualisiert von: h7k

Kommentar Antworten

I think that dir_adjust_append_vlist (in ltj-lineskip.lua) is probably the cause of this error, but I'm still investigating...

2022-08-06 08:41 Aktualisiert von: h7k

Kommentar Antworten

Although LuaTeX-ja has several memory leaks (I'm working on these), fixing this "stack overflow" error requires the recompilation of LuaTeX binary (see a thread starting from here).

You can use following workaround (but this makes luatexja-adjust.sty useless):

 \usepackage{luatexja}
 ...
 \directlua{
   luatexbase.remove_from_callback('append_to_vlist_filter', 'ltj.lineskip')
 }
 ...
 \begin{document}

2022-08-09 01:06 Aktualisiert von: None

Kommentar Antworten

Thank you. Your workaround works!

2023-02-26 09:17 Aktualisiert von: h7k

• Status Update from Offen to Geschlossen
• Lösung Update from Keine to Gefixt

Kommentar Antworten

Although LuaTeX-ja has several memory leaks (I'm working on these), fixing this "stack overflow" error requires the recompilation of LuaTeX binary (see a thread starting from here).

LuaTeX binaries in TeX Live 2023 (which is now pretesting) should fix this issue. So I close this ticket.