From: David Wooten <dw@trichotomic.net>
Subject: Re: Font memory issues ?
Date: Tue, 17 Jan 2006 15:15:42 -0800 [thread overview]
Message-ID: <85824E5F-150A-4456-AF00-1006FAEF14A5@trichotomic.net> (raw)
In-Reply-To: <43CD718A.5080405@wxs.nl>
Hans, is this what you're referring to?
kdebug:hash_lookup(main_memory.context) => 3000000 % Keep total
within 8000000 limit 3000000 % Keep total within 8000000 limit
kdebug:variable: main_memory = 3000000 % Keep total within 8000000 limit
kdebug:hash_lookup(font_mem_size.context) => 3000000
kdebug:variable: font_mem_size = 3000000
kdebug:hash_lookup(font_max.context) => (nil)
kdebug:hash_lookup(font_max) => 2000
kdebug:variable: font_max = 2000
If so, the increases I've made are evident here. . . but not when I
run texexec?
On Jan 17, 2006, at 2:36 PM, Hans Hagen wrote:
> David Wooten wrote:
>
>> At this point I would very much like to be embarrassed by a
>> simple, too-obvious pointer ;)
>
> how about generating a plain tex format using
>
> pdfetex --ini
>
> and enabling the kpse debug options? Then you can see what is used:
>
> pdfetex --kpathsea-debug=65535 --ini --progname=context plain
>
> Hans
next prev parent reply other threads:[~2006-01-17 23:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 19:07 David Wooten
2006-01-10 19:17 ` Font memory issues ? : bib-module? David Wooten
2006-01-10 20:22 ` Taco Hoekwater
2006-01-10 21:54 ` Font memory issues ? Hans Hagen
2006-01-11 0:39 ` David Wooten
2006-01-11 8:16 ` Hans Hagen
2006-01-11 23:17 ` David Wooten
2006-01-12 7:25 ` Thomas A. Schmitz
2006-01-12 8:28 ` Hans Hagen
2006-01-12 19:04 ` David Wooten
2006-01-12 20:02 ` Taco Hoekwater
2006-01-12 22:49 ` David Wooten
2006-01-13 0:15 ` Taco Hoekwater
2006-01-12 20:05 ` Hans Hagen
2006-01-12 22:48 ` David Wooten
2006-01-16 23:18 ` David Wooten
2006-01-17 10:15 ` Thomas A. Schmitz
2006-01-17 17:35 ` David Wooten
2006-01-17 18:31 ` Thomas A. Schmitz
2006-01-17 21:46 ` David Wooten
2006-01-17 22:36 ` Hans Hagen
2006-01-17 23:15 ` David Wooten [this message]
2006-01-19 19:41 ` David Wooten
2006-01-19 20:16 ` Taco Hoekwater
2006-01-19 20:28 ` Taco Hoekwater
2006-01-19 21:44 ` Hans Hagen
2006-01-19 22:37 ` Taco Hoekwater
2006-01-19 23:47 ` David Wooten
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=85824E5F-150A-4456-AF00-1006FAEF14A5@trichotomic.net \
--to=dw@trichotomic.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).