[metapost] Metapost capacity exceeded
taco at elvenkind.com
Thu Jun 3 20:32:42 CEST 2010
> Here is how much of MetaPost's memory you used:
> 0i,71n,0p,104b,1f stack positions out of 300i,84n,10000p,200b,15f
> 0 string compactions (moved 0 characters, 0 strings)
Not all stats are the same between in metafont and metapost,
you deduced that correctly.
> But (8) seems to correspond to the 7th number
> (0p/10000p), which in turn looks like param_size; and (5) seems to
> correspond to the 9th number (1f/15f), which looks like max_in_open. Am
> I guessing right? How about the rest?
> 0i ->
This is (5). It is dynamically reallocated if needed, and starts
out at 300. In metafont this was the 'stack_size' parameter in
texmf.cnf, I believe.
> 71n -> (6)
Yes. Also dynamically reallocated (already reallocated once,
as 84 == 70 * 1.2).
> 0p -> (8)
Yes (there is no (7) 'rounding table size' in metapost)
> 104b -> ?
This is (9). It is also dynamically reallocated if needed.
> 1f -> (5)
No this is not (5), this is new to metapost, and it is the
max_in_open, as you guessed.
More information about the metapost