Oh dear - I shouldn't have said anything - sorry, I have no time to deal
with this. All I can say is that if there was a memory leak in FreeType it
would show up in all sorts of places - not just in Symbian OS. I suspect
it's a problem in the calling code.
I recently had heap corruption problems,
> Src/base/ftsystem.c
> FT_CALLBACK_DEF( void* )
> ft_alloc( FT_Memory memory,
> long size )
> {
> FT_UNUSED( memory );
>
> return ft_smalloc( size );// memory leak
>
> }
>
> You can have a look at the attached jepg for more information.
Thanks. I've fo
> In the FtViewer, after the function “FTC_ImageCache_LookupScaler” was call,
> I can get the two value:
>
> dXAdvance = (glyph->advance.x) >> 16;
> dYAdvance = (glyph->advance.y) >> 16;
>
> And what I want to know is how to get the values without calling the
> function “FTC_ImageCache_LookupSc
>First, It is a great open source projectJ I am Hong Li, from
> china. Actually I have already ported freetype to symbian but I saw
> memory leak in your code. you use malloc and free which don't work
> well on symbian. I use the hook Logger tool to confirm that there
> is memory leak..
Int
FreeType has been used successfully on Symbian OS for about ten years. I was
the one who put it there. malloc and free work perfectly on that platform as
far as I remember. There may be a memory leak, but I don't think it is
caused by a problem with the malloc and free implementations on Symbian OS
Hi ALL,
First, It is a great open source projectJ I am Hong Li, from china.
Actually I have already ported freetype to symbian but I saw memory leak in
your code. you use malloc and free which don't work well on symbian.I use
the hook Logger tool to confirm that there is memory leak..
> 1) FT_Outline_Decompose() does not walk through all the Outline
> contour-points one-by-one and call the emitters.
>
> By printing out the to_points passed to the emitters by
> FT_Outline_Decompose(), we noticed that there are gaps. The
> decomposition begins with a consecutive sequence follow
