Re: [Devel] Memory leak in FT2 (before new pshinter commit)

[Tom Kacvinsky]

Yep, that was it -- there were problems with parsing synthetic fonts.  There was
already code in place to make sure that the FontMatrix and CharStrings didn't
get read twice, but there was no test on whether the FontName or Subrs array was
already.  So what was happening is that these objects were allocated twice, but
the first object was never deallocated.

I am in the middle of chatting with a fellow from California about fixing some
bugs in dvips, so it will be a while before the commit happens.

Tom

On Sat, 20 Oct 2001, Tom Kacvinsky wrote:

> As far as I can tell, the problem is triggered by parsing synthetic fonts 
> (like
> Helvetica-Oblique, Courier-Oblique, etc...).  At least I have something to go 
> on
> now...
>
> Tom
>
> On Sat, 20 Oct 2001, Tom Kacvinsky wrote:
>
> > Hmmm... Are you using the Type 1 driver, or the TT driver?  The problem I 
> > see is
> > with the Type 1 driver.  I do not see the problem with the OpenType driver,
> > either.
> >
> > Tom
> >
> > On Sat, 20 Oct 2001, walker wrote:
> >
> > > Ohhhh, I tested my ft2 demo  with Boundschecker in win2000, and no memory 
> > > leak found.
> > >
> > > Of course, My demo is too simple and maybe did not get the right way to 
> > > find
> > > memory leak. Please drop me a email if need my boundschecker's help.
> > >
> > > Reagrds.
> > >
> > >
> > > Walker.
> > >
> > > ----- Original Message -----
> > > From: "Tom Kacvinsky" <address@hidden>
> > > To: "FreeType Development" <address@hidden>
> > > Sent: Saturday, October 20, 2001 3:10 AM
> > > Subject: [Devel] Memory leak in FT2 (before new pshinter commit)
> > >
> > >
> > > > It has been reported on this list that there is memory leak in FT2, 
> > > > using the
> > > > code prior to the pshinter module commit.
> > > >
> > > > As I don't have purify (what a great product, based on the demo I had), 
> > > > I tried
> > > > using Electric Fence.  That did no good.  ftmemchk reports that there 
> > > > leaks.
> > > >
> > > > I suspect that the leak stems from something in the pasux module 
> > > > (specifically,
> > > > psobjs.c), but I haven't been able to track this down.
> > > >
> > > > Any one have any ideas?  In the meantime, I am going to ping my bosses 
> > > > about
> > > > getting a license for purify.  If anyone wants to step up and buy the 
> > > > FreeType
> > > > team a copy of purify (I would prefer a copy for Solaris), please let 
> > > > me know.
> > > > It would be appreciated.  Or, perhaps someone with a license for purify 
> > > > can
> > > > check the code and report back where the leak is happening, and I will 
> > > > commit
> > > > the necessary changes.
> > > >
> > > > Regards,
> > > >
> > > > Tom
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Devel mailing list
> > > > address@hidden
> > > > http://www.freetype.org/mailman/listinfo/devel
> > >
> >
> >
> >
> > _______________________________________________
> > Devel mailing list
> > address@hidden
> > http://www.freetype.org/mailman/listinfo/devel
> >
>
>
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel
>