Memory problem in Pango?



Hi all.

I was debugging a program of mine, and when I ran valgrind, I ran across
the following (which sounds quite important):

==30953==  Address 0x5F73D25 is 141 bytes inside a block of size 1,280 free'd
==30953==    at 0x401A2F8: free (m_replacemalloc/vg_replace_malloc.c:233)
==30953==    by 0x46B5DA9: _cairo_traps_fini (cairo-traps.c:84)
==30953==    by 0x46A5F46: _cairo_clip_clip (cairo-clip.c:461)
==30953==    by 0x46A86BB: _cairo_gstate_clip (cairo-gstate.c:1125)
==30953==    by 0x46A3BD8: cairo_clip_preserve (cairo.c:2034)
==30953==    by 0x46A3C01: cairo_clip (cairo.c:2001)
==30953==    by 0x45C69DF: _gdk_gc_update_context (gdkgc.c:1243)
==30953==    by 0x45C7E7D: get_cairo_context (gdkpango.c:207)
==30953==    by 0x45C7FA6: gdk_pango_renderer_draw_glyphs (gdkpango.c:232)
==30953==    by 0x46801F0: pango_renderer_draw_glyphs (pango-renderer.c:597)
==30953==    by 0x468159C: pango_renderer_draw_layout_line (pango-renderer.c:528)
==30953==    by 0x468194A: pango_renderer_draw_layout (pango-renderer.c:182)

Could this be a cause for concern?

John



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]