On 8/14/2020 2:38 AM, Jannik Voges wrote:

Hello,

I have a similar problem with long context-documents (but not all long context-documents are affected and I don't know what triggers the error). Sometimes, the errors (error code 139) are happening on second or third runs (but it might happen on first runs too). When I remove the chapter where the error happens and all later chapters from the document it might happen, that the error occures in an earlier chapter. In addition to that, documents, which had this error yesterday, can now be compiled without the problem and other documents without the error yesterday have the error today. Its really strange.

i uploaded a new lmtx but as i'm in the middle of a few things it's a gamble if that solves your problem Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

On 8/14/2020 9:26 AM, Pablo Rodriguez wrote:

Latest from 2020.08.11 works fine for my huge document, but current latest (from today) breaks compilation. So I use latest from 2020.08.11.

i really need a MWE example then .. all runs well here Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

On 8/15/2020 5:25 PM, Pablo Rodriguez wrote:

Which is the meaning of error number 139? It might help me to know what I should be looking at. Hm, but does the current version also quit? I fixed a mp issue.

Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

On 8/15/20 8:14 PM, Pablo Rodriguez wrote:

On 8/15/20 7:23 PM, Hans Hagen wrote:

...

On 8/15/2020 5:25 PM, Pablo Rodriguez wrote:

...

Which is the meaning of error number 139? It might help me to know what I should be looking at. Hm, but does the current version also quit? I fixed a mp issue.

The version that works for me is 2020.08.09. Some previous versions didn’t work. And versions from 2020.08.11 and both from 2020.08.14 quit.

I have just checked and version from 2020.08.11 work too. Both versions from 2020.08.14 quit. I will hunt for the bug next month. Pablo -- http://www.ousia.tk

Hello Pablo, thank you for your suggestions, but I don't use LMTX productively, so I have no problem with a broken LMTX-version. I only use it to check whether there are breaking changes in LMTX by typesetting all of my documents with the newest LMTX-version (to see if I need to change them in the future). And by doing so I recognized this error, which seemed to happen randomly. Jannik Am 14.08.20 um 09:26 schrieb Pablo Rodriguez:

On 8/14/20 8:47 AM, Hans Hagen wrote:

...

On 8/14/2020 2:38 AM, Jannik Voges wrote:

...

[...] I have a similar problem with long context-documents (but not all long context-documents are affected and I don't know what triggers the error). Sometimes, the errors (error code 139) are happening on second or third runs (but it might happen on first runs too). When I remove the chapter where the error happens and all later chapters from the document it might happen, that the error occurs in an earlier chapter. In addition to that, documents, which had this error yesterday, can now be compiled without the problem and other documents without the error yesterday have the error today. Its really strange.

i uploaded a new lmtx but as i'm in the middle of a few things it's a gamble if that solves your problem

Jannik,

it is wise to make a backup of your installed ConTeXt version when updating. Especially now that LMTX is in testing mode.

Latest from 2020.08.11 works fine for my huge document, but current latest (from today) breaks compilation. So I use latest from 2020.08.11.

Just in case it helps,

Pablo -- http://www.ousia.tk ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________

On 8/14/2020 11:41 AM, Jannik Voges wrote:

Hello Pablo,

thank you for your suggestions, but I don't use LMTX productively, so I have no problem with a broken LMTX-version. I only use it to check whether there are breaking changes in LMTX by typesetting all of my documents with the newest LMTX-version (to see if I need to change them in the future). And by doing so I recognized this error, which seemed to happen randomly. you can try to run with

\tracingall and/or \enabletrackers[*] and see where it crashes Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

Hello Lutz, I can confirm this. Compiling luametafun.tex (see luametafun.zip; I included the log-file, but the log-file doesn't include all the output I can see on the console (therefore I included the file output_console.txt with a copy of my console-output). I used linux aarch64. Yes, commenting things out in my own tex-documents might result in a successful compilation, but I had a document (which compiles normaly now, but not two days before) where I got the same error at another position in the file (after deleting all chapters after the one where the error occurred including the one with the error). Greetings Jannik Am 14.08.20 um 13:38 schrieb Lutz Haseloff:

Hi all

I have a similar problem compiling luametafun.tex in the doc sources. It fails with different errorcodes on win64 and linux aarch64. On linux aarch64 i get a bonus "Segmentation fault". I append the console outputs of the context runs.

If i comment out the input of luametafun-axis and luametafun-followtext i get a readeable pdf.

So perhaps only the code is changing too rapidly.

Greetings Lutz

Am 14. August 2020 13:04:52 MESZ schrieb Hans Hagen :

On 8/14/2020 11:41 AM, Jannik Voges wrote:

Hello Pablo,

thank you for your suggestions, but I don't use LMTX productively, so I have no problem with a broken LMTX-version. I only use it to check whether there are breaking changes in LMTX by typesetting all of my documents with the newest LMTX-version (to see if I need to change them in the future). And by doing so I recognized this error, which seemed to happen randomly.

you can try to run with

\tracingall

and/or

\enabletrackers[*]

and see where it crashes

Hans ------------------------------------------------------------------------ Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl ------------------------------------------------------------------------ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ------------------------------------------------------------------------

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________

Hello Hans, I get the error with the newest upload too. Jannik Am 14.08.20 um 08:47 schrieb Hans Hagen:

On 8/14/2020 2:38 AM, Jannik Voges wrote:

...

Hello,

I have a similar problem with long context-documents (but not all long context-documents are affected and I don't know what triggers the error). Sometimes, the errors (error code 139) are happening on second or third runs (but it might happen on first runs too). When I remove the chapter where the error happens and all later chapters from the document it might happen, that the error occures in an earlier chapter. In addition to that, documents, which had this error yesterday, can now be compiled without the problem and other documents without the error yesterday have the error today. Its really strange.

i uploaded a new lmtx but as i'm in the middle of a few things it's a gamble if that solves your problem

Hans

-----------------------------------------------------------------                                           Hans Hagen | PRAGMA ADE               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________

If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage  : http://www.pragma-ade.nl / http://context.aanhet.net archive  : https://bitbucket.org/phg/context-mirror/commits/ wiki     : http://contextgarden.net ___________________________________________________________________________________

Hi Wolfgang, thats a little bit difficult, because the error apparently happens at a random position in the document (you can add a syntax error in the document an change the position of the syntax error in the document until lmtx crashes before it detects the error to get the paragraph where the crash happens, but that paragraph is fine). And I don't know why the error happens in one document and not in others (I use similar commands in affected and not-affected documents; the affected documents are long but not the longest documents I have) or why it happened two days ago in one document, which is fine today, and today at another document (which was fine two days ago). So I don't have a clue how to reproduce the error. Jannik Am 14.08.20 um 11:33 schrieb Wolfgang Schuster:

Jannik Voges schrieb am 14.08.2020 um 11:29:

...

Hello Hans,

I get the error with the newest upload too.

You have to provide a minimal example which produces the error.

Wolfgang