From: Peter Rolf <indiego@gmx.net>
To: ntg-context@ntg.nl
Subject: Re: luatex crash around page 1000
Date: Fri, 12 Apr 2019 11:04:31 +0200 [thread overview]
Message-ID: <8297edf4-17ee-d1b6-c705-adc8608a6dce@gmx.net> (raw)
In-Reply-To: <690E734979364961886E9710C7BFCA54@CJ3001517A>
Am 12.04.2019 um 07:36 schrieb Akira Kakuto:
>> mtx-context | fatal error: return code: -1073741571
>
> I suspect that may be a limitation in 32bit binary.
> Try to install 64bit ConTeXt if you are using 32bit one
> and your OS is 64bit.
>
I'm already on 64bit, so that won't help here.
The event manager says, that it is a stack exhaustion (0xc00000fd,
STATUS_STACK_OVERFLOW).
The PDF is data driven and I need to call a lot of functions per page to
collect all components and values for a complete 'Mech. This seems to
sum up and I just run out of stack memory after around 1000 pages.
Screenshots from the event manager (application error), Process Explorer
(peak memory values) and an outdated version of the PDF can be found here
https://spideroak.com/browse/share/indiego/public/RogueTech/
Peter
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-04-12 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 5:36 Akira Kakuto
2019-04-12 6:06 ` luigi scarso
2019-04-12 7:22 ` Hans Hagen
2019-04-12 9:04 ` Peter Rolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-12 10:47 Akira Kakuto
2019-04-11 10:28 Peter Rolf
2019-04-11 11:52 ` Hans Hagen
2019-04-11 15:16 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8297edf4-17ee-d1b6-c705-adc8608a6dce@gmx.net \
--to=indiego@gmx.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).