![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Hi, Hartmut Henkel wrote:
On Wed, 15 Nov 2006, Taco Hoekwater wrote:
This turned out to be something completely different from what I thought initially, and does not seem related to a font number limit at all ?
now it seems to be some kind of memory leak: Something spills over into the font_used[f] array, setting it successively true from the beginning. When font no. 90 is loaded, it's just full enough so that this font is never initialized. Then it crashes. Guarding the font_used[f] array in front by some additional dummy boolean foo_used[f] array helps, then it runs fine. One also sees that then array foo_used[] is filled with true. No idea yet what this leak is.
I think I have found it from checking up your hint about font_used[] in the debugger: The arrays vf_i_fnts[] and vf_e_fnts[] are alloc as size font_max, but their indexes can easily overflow that because a vf font can contain more than one base font. I've added two cases of if vf_nf>font_max then overflow("virtual fonts",font_max); right after the two occurrences of increments of vf_nf in pdftex.web, and now I get: ! TeX capacity exceeded, sorry [virtual fonts=2000]. Cheers, Taco