ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 620 pages limit?
Date: Mon, 14 Mar 2011 21:14:27 +0100	[thread overview]
Message-ID: <4CA431C4-AF53-4008-844E-A77312A6D068@st.estfiles.de> (raw)
In-Reply-To: <F629FF48-7713-4A66-8454-CAD68A47FDD2@st.estfiles.de>


Am 14.03.2011 um 17:53 schrieb Steffen Wolfrum:

> 
> Am 14.03.2011 um 17:22 schrieb Taco Hoekwater:
> 
>> On 03/14/2011 05:08 PM, Steffen Wolfrum wrote:
>>> Hi,
>>> 
>>> in December we had 4000 pages limit, now I only reach 700 pages limit:
>>> 
>>> pages>  flushing realpage 615, userpage 619
>>> pages>  flushing realpage 616, userpage 620
>>> PANIC: unprotected error in call to Lua API (stack overflow (out of stack space))
>>> 
>>> mtx-context     | fatal error: return code: 1
>>> 
>>> It's a book wih 7 chapters, each of it run fine. Only typesetting the entire project (not even with TOC) gives this error.
>>> Is there help?
>> 
>> That is clearly a bug somewhere, but it needs a minimal demonstration
>> file from you. A simple
>> 
>> \dorecurse{5000} {\input knuth \page }
>> 
>> does not trigger it.
> 
> 
> My context-minimal *does* trigger the PANIC with 5000 Knuth-pages!
> Do I need to change the LuaTeX part of the minimal installation?
> 
> ConTeXt  ver: 2011.02.25 22:03 MKIV
> This is LuaTeX, Version beta-0.65.0-2010121316 



btw, running on MacOSX (same as reported on Linux 64bit)

Steffen
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-03-14 20:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 16:08 Steffen Wolfrum
2011-03-14 16:22 ` Taco Hoekwater
2011-03-14 16:53   ` Steffen Wolfrum
2011-03-14 20:14     ` Steffen Wolfrum [this message]
2011-03-14 17:02   ` luigi scarso
2011-03-14 18:51     ` Vnpenguin
2011-03-14 21:45       ` Steffen Wolfrum
2011-03-14 22:00         ` Hartmut Henkel
2011-03-15  9:07       ` Vnpenguin
2011-03-15 10:27         ` Steffen Wolfrum
2011-03-15 14:44           ` Steffen Wolfrum
2011-03-15 15:35             ` Taco Hoekwater
2011-03-15 15:59               ` Otared Kavian
2011-03-15 19:00                 ` Marco
2011-03-15 16:11               ` Steffen Wolfrum
2011-03-15 16:20                 ` Taco Hoekwater
2011-03-15 17:29                   ` Steffen Wolfrum
2011-03-16 17:15                     ` 620 pages limit? (SOLVED) Steffen Wolfrum
2011-03-14 20:44     ` 620 pages limit? Vedran Miletić
2011-03-14 20:58       ` Cecil Westerhof
2011-03-14 21:22       ` mathew
2011-03-14 21:35     ` Wolfgang Schuster
2011-03-14 22:15       ` Procházka Lukáš
2011-03-14 22:56         ` C.
2011-03-15 17:18       ` Vnpenguin
2011-03-16 16:54       ` Hans Hagen
2011-03-17  6:28         ` Vnpenguin
2011-03-18  9:55           ` 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=4CA431C4-AF53-4008-844E-A77312A6D068@st.estfiles.de \
    --to=context@st.estfiles.de \
    --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).