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>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: project too large??
Date: Wed, 10 Sep 2008 21:41:30 +0200	[thread overview]
Message-ID: <6715D0FD-2BDC-40F8-9CEE-2AF17764456B@st.estfiles.de> (raw)
In-Reply-To: <D5CCA5D8-252E-43CB-AF8A-1D6E0844049E@st.estfiles.de>

... ok fine again. I just increased the weak settings by ten:

hash_extra = 500000 % 50000
pool_size.context        = 20000000 % 2000000

But I assume the fact that these variables have predefined values  
indicates that they shouldn't be fantastic high. Otherwise why would  
they have these precise values anyway?

So I am wondering: what is the right value, what is too high and what  
happens if the values are too high?

Steffen



Am 10.09.2008 um 18:46 schrieb Steffen Wolfrum:

>
> Am 09.09.2008 um 18:38 schrieb Hans Hagen:
>
>> Steffen Wolfrum wrote:
>>> Hi,
>>>
>>> I have a quite large project: over 700 pages, 2500 footnotes, some
>>> tables, figures etc.
>>> Everything works well when typeset in two parts.
>>>
>>> But when I typeset the entire project as one, I get this error:
>>>
>>>
>>>>
>>>
>>> EbeneSechs      : C.III.7.b Wirksamkeit trotz mündlicher und
>>> konkludenter Abtr
>>> etungsverbote
>>> ! TeX capacity exceeded, sorry [hash size=60000].
>>
>> you can increase the hash in texmf.cnf
>
>
> that worked ... but after some more working on my project I get
> another error (see below):
>
> which one I can increase now ?
>
> pool_free.context        =   47500
> pool_size.context        = 2000000
> pool_size = 1250000
> pool_free = 47500
>
> Thanks, Steffen
>
> =====
>
> ! TeX capacity exceeded, sorry [pool size=529543].
> \defconvertedargument ...\edef #1{\detokenize {#2}
>                                                   }
> \dodododoconstructhead ...ko #1\c!expansion }}{#4}
>                                                   \gdef
> \currentheadtext {#4...
> l.3933 ...\kern-0.05em}, \hbox{ZfgKW} 2005, 981.]}
>
> If you really absolutely need more capacity,
> you can ask a wizard to enlarge me.
>
>
> Here is how much of TeX's memory you used:
>  33083 strings out of 457141
>  529543 string characters out of 529543
>  5331289 words of memory out of 7759285
>  61694 multiletter control sequences out of 10000+500000
>  1283787 words of font info for 969 fonts, out of 3000000 for 5000
>  543 hyphenation exceptions out of 8191
>  72i,21n,94p,4610b,14879s stack positions out of 5000i,500n,10000p,
> 200000b,50000s
> !  ==> Fatal error occurred, no output PDF file produced!
>
> ___________________________________________________________________________________
> 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  : https://foundry.supelec.fr/projects/contextrev/
> 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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-09-10 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 16:26 Steffen Wolfrum
2008-09-09 16:38 ` Hans Hagen
2008-09-09 17:03   ` Idris Samawi Hamid ادريس سماوي حامد
2008-09-09 17:39     ` Hans Hagen
2008-09-10 16:46   ` Steffen Wolfrum
2008-09-10 19:41     ` Steffen Wolfrum [this message]
2008-09-10 19:57       ` Hans Hagen
2008-09-10 20:34       ` Thomas A. Schmitz

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=6715D0FD-2BDC-40F8-9CEE-2AF17764456B@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).