warning (hpack filter): stack overflow

• Relator: henribranken
• Dono: h7k
• Tipo: Bugs
• Estado: Fechado
• Componente: (Nenhum)
• Marcos: (Nenhum)
• Prioridade: 7
• Gravidade: 7
• Resolução: Fixed
• Arquivo: Nenhum

Details Responder

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 History (3/7 Histories)

2022-08-02 20:08 Updated by: henribranken

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

2022-08-02 20:18 Updated by: h7k

• Dono Update from (Nenhum) to h7k
• Tipo Update from Support Request to Bugs

Comentário Responder

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

2022-08-02 20:43 Updated by: h7k

Comentário Responder

Smaller example:

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

2022-08-04 18:47 Updated by: h7k

Comentário Responder

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 Updated by: h7k

Comentário Responder

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 Updated by: None

Comentário Responder

Thank you. Your workaround works!

2023-02-26 09:17 Updated by: h7k

• Estado Update from Aberto to Fechado
• Resolução Update from Nenhum to Fixed

Comentário Responder

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.