![](https://secure.gravatar.com/avatar/ad5afbb91c8b5ec2b1199838461a8348.jpg?s=120&d=mm&r=g)
15 Nov
2006
15 Nov
'06
5:23 p.m.
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. Regards, Hartmut