Re: Memory errors in pango, thoughts on making it optional?

	Hi Allin,

On Thu, 2004-12-02 at 18:45 -0500, Allin Cottrell wrote:
> On Thu, 2 Dec 2004, Al Hooton wrote:
> 
> > 	Like: I'm seeing a *lot* of memory problems down in Pango. 
> > Enough to be disturbing...
> 
> If you're reasonaably sure the pango memory issues are not spurious, 
> I'd take them to the gtk-devel mailing list. 

	Yes, I agree.  Actually, when your email came in, I was on the gtk.org
site thinking through exactly the best way to do this (which list,
and/or bugzilla, etc.).  I will definitely be doing this and seeing how
it does down that path.

>  It's a bit hard on 
> Adrian to ask him to work around bugs at a lower level in the GUI 
> apparatus.
> 
	While I agree with you, based on a cursory look at the what the Pango
project has going on now (lots of activity), I fear that it may take a
while for things like low-level memory access issues to be addressed.  I
respect the Pango team for what it's trying to do -- they've tackled a
hard problem, with the ever-present issue of limited resources.  But
that leads me to the concern that it might take a while.

	What I'm suggesting is essentially just a "backing out" of the changes
to add Pango to gtkextra-2, and going back to the previous string
handling/rendering machinery.  I don't know if it's possible, or easy,
or even advisable at this point, because I haven't dug in to those parts
of gtkextra-2 enough to form my own opinion.  That's why I'm looking for
Adrian's.  Icing on the cake would be if we could switch between the old
machinery and Pango with compile-time switches, but I realize that is
yet harder.

-Al





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/