Hi Guys, could you enable the FreType built-in debugger to determine where the leak is ? see the DEBUG file in docs/ for instructions on how to do that, that would be useful.
thanks in advance, - David On Mon, 11 Jun 2007 08:57:15 -0400, "Chris Altick" <[EMAIL PROTECTED]> said: > I'm noticing a similar problem, when I try to hold more than one face in > memory retrieving the characters from the Cache with the > FTC_ImageCache_Lookup function I'll eventually use all the memory up. So > to work around this I severely decrease the performance by calling > FTDemo_Done which cleans up, every time I change point size of font face. > > I watched the Cache addresses created for the glyphs and they seemed to > stay in my user defined maximum size for the cache, so the memory must be > used in other areas. > > Chris > > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf > of DingLi(??) > Sent: Mon 6/11/2007 6:17 AM > To: [email protected] > Subject: [ft-devel] Memory problem? > > I use the freetype 2.3.1 in my project. When I parse thousands of > fonts(of course they are very small), the memory increase rapidly to more > than 230M, and it's a continued growth. > > My older version use the freetype 2.0.9, it increase very slow, and stop > grow finally. > > > > Does it is a bug or a problem when I use? > > I use functions: > > FT_New_Memory_Face > > FTC_ImageCache_Lookup > > ... > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > _______________________________________________ Freetype-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype-devel
