From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Font memory issues ? : bib-module?
Date: Tue, 10 Jan 2006 22:53:33 +0100 [thread overview]
Message-ID: <43C42CDD.2010607@elvenkind.com> (raw)
In-Reply-To: <93050b0e99f3462f80fca1bd282eac93@localhost>
David Wooten wrote:
> Here are the stats, after removing placepublications:
>
> Here is how much of TeX's memory you used:
> 4760 strings out of 60999
> 76752 string characters out of 611011
> 32604822 words of memory out of 34111765
> 40674 multiletter control sequences out of 10000+50000
> 1974579 words of font info for 355 fonts, out of 2000000 for 2000
That's cutting it close:
2000000-1974579 = 25421.
Another five extra fonts (or so) being loaded will 'do it'.
You have to increase font_mem_size, my guess is this limit is
triggered by nothing but 'normal operation' (not a bug).
Good luck, Taco
next prev parent reply other threads:[~2006-01-10 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 21:13 David Wooten
2006-01-10 21:53 ` Taco Hoekwater [this message]
2006-01-10 22:01 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2006-01-10 19:07 Font memory issues ? David Wooten
2006-01-10 19:17 ` Font memory issues ? : bib-module? David Wooten
2006-01-10 20:22 ` Taco Hoekwater
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=43C42CDD.2010607@elvenkind.com \
--to=taco@elvenkind.com \
--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).