From: "Willi Egger" <w.egger@boede.nl>
Subject: Re: TeX capacity exceeded in MikTeX
Date: Sun, 28 Sep 2003 14:42:59 +0200 [thread overview]
Message-ID: <00ce01c385be$375825b0$0100a8c0@vademecum> (raw)
In-Reply-To: <116146190490.20030928105606@emil.teleton.pl>
Find in the texmf.cnf file in texmf-var\web2c directory the section where
the different memory settings are set:
The following table was posted by Hans Hagen in february 2003, so it should
be o.k. At least in my situation these settings do perform as expected.
buf_size.context = 200000 % needed for omega bug
extra_mem_bot.context = 2000000
extra_mem_top.context = 2000000
font_max.context = 2000
font_mem_size.context = 1000000
hash_extra.context = 50000
main_memory.context = 1500000
max_strings.context = 100000
nest_size.context = 500
obj_tab_size.context = 300000
dest_names_size = 300000
param_size.context = 5000
pool_free.context = 47500
pool_size.context = 1250000
save_size.context = 50000
stack_size.context = 5000
string_vacancies.context = 90000
main_memory.mpost = 2000000
pool_size.mpost = 200000
Willi
----- Original Message -----
From: "^Nitram^" <nitram@emil.teleton.pl>
To: <ntg-context@ntg.nl>
Sent: Sunday, September 28, 2003 10:56 AM
Subject: [NTG-context] TeX capacity exceeded in MikTeX
> Hi,
>
> I have the same problem as was reported at 8.04.2003 - anybody
> resolved it ?... I have a document (about 80 pages) and error when I
> compile whole. Below I attach my log file - anybody have any good idea
> - I need this paper today ;(((
>
> log file:
> [cut]
> ! TeX capacity exceeded, sorry [hash size=35000].
>
> 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:
> 6324 strings out of 67199
> 81075 string characters out of 744379
> 601426 words of memory out of 1165764
> 35000 multiletter control sequences out of 35000
> 41684 words of font info for 101 fonts, out of 500000 for 1000
> 96 hyphenation exceptions out of 607
> 63i,21n,91p,1354b,3886s stack positions out of
1500i,500n,5000p,200000b,32768s
> 973 PDF objects out of 65536
> 480 named destinations out of 20000
> 9 words of extra memory for PDF output out of 65536
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2003-09-28 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 8:56 ^Nitram^
2003-09-28 12:42 ` Willi Egger [this message]
2003-09-28 15:23 ` Re[2]: " ^Nitram^
2003-09-28 16:14 ` Willi Egger
2003-09-28 16:28 ` ^Nitram^
2003-09-29 8:20 ` Jochen Dietrich
2003-09-28 18:35 ` Giuseppe Bilotta
2003-09-29 7:55 ` Sebastian Rooks
2003-09-29 18:55 ` walter kehowski
2003-09-29 19:16 ` Patrick Gundlach
2003-09-29 9:00 ^Nitram^
2003-09-29 10:29 ` 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='00ce01c385be$375825b0$0100a8c0@vademecum' \
--to=w.egger@boede.nl \
--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).