Re: [patch] Rework of Pango integration
- From: Jody Goldberg <jody gnome org>
- To: Owen Taylor <otaylor redhat com>
- Cc: gnome-print-list gnome org, Jean Br?fort <jean brefort ac-dijon fr>
- Subject: Re: [patch] Rework of Pango integration
- Date: Wed, 9 Jun 2004 13:27:52 -0400
On Wed, Jun 09, 2004 at 12:48:14PM -0400, Owen Taylor wrote:
> On Wed, 2004-06-09 at 12:19, Jody Goldberg wrote:
>
> > That is not the core of the problem. Portions of the related
> > layouts remain behind. We're seeing things like :
> >
> > MLK: 192 bytes leaked in 6 blocks
> > * This memory was allocated from:
> > malloc [rtlib.o pc=0x6a3c8]
> > g_malloc [gmem.c:136 pc=0xf9e56888]
> > pango_ft2_font_render_glyph [pangoft2.c:314 pc=0xfb03afb8]
> > pango_ft2_render [pangoft2.c:384 pc=0xfb03b45c]
> > pango_ft2_render_layout_line [pangoft2.c:790 pc=0xfb03c3ac]
> > pango_ft2_render_layout [pangoft2.c:884 pc=0xfb03ca98]
> >
> > Even when the layout has been unrefed. If it was just the global
> > singleton this would be less significant.
>
> This is just caching... it should be reachable from the fontmap,
> right?
That's our current theory. Unfortunately it makes enough of a mess
that I'd like some way to clear it out. Checking for real leaks get
alot more difficult if this sort of thing clouds the waters. How
about a pango extension to clear the default fontmap ?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]