THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#357 - git-awesome leaks memory
User who did this - Maarten Maathuis (madman2003)

----------
That would be on linux, the leak is present in the cairo-xcb backend for every 
released cairo.

It shows up as this (From my own valgrinding, yours does not show this):

==25294== 84,192 bytes in 471 blocks are definitely lost in loss record 140 of 
143
==25294==    at 0x4C23018: malloc (vg_replace_malloc.c:207)
==25294==    by 0x6CE6907: _cairo_xcb_surface_show_glyphs (in 
/usr/lib64/libcairo.so.2.10901.0)
==25294==    by 0x6CCF48E: _cairo_surface_show_text_glyphs (in 
/usr/lib64/libcairo.so.2.10901.0)
==25294==    by 0x6CBCC56: _cairo_gstate_show_text_glyphs (in 
/usr/lib64/libcairo.so.2.10901.0)
==25294==    by 0x6CB85D0: cairo_show_glyphs (in 
/usr/lib64/libcairo.so.2.10901.0)
==25294==    by 0x504CC72: pango_cairo_renderer_show_text_glyphs (in 
/usr/lib64/libpangocairo-1.0.so.0.2202.0)
==25294==    by 0x504CD09: pango_cairo_renderer_draw_glyph_item (in 
/usr/lib64/libpangocairo-1.0.so.0.2202.0)
==25294==    by 0x5275E70: pango_renderer_draw_glyph_item (in 
/usr/lib64/libpango-1.0.so.0.2202.0)
==25294==    by 0x52763BA: pango_renderer_draw_layout_line (in 
/usr/lib64/libpango-1.0.so.0.2202.0)
==25294==    by 0x52767FF: pango_renderer_draw_layout (in 
/usr/lib64/libpango-1.0.so.0.2202.0)
==25294==    by 0x504BA65: _pango_cairo_do_layout (in 
/usr/lib64/libpangocairo-1.0.so.0.2202.0)
==25294==    by 0x42419F: draw_text (draw.c:441)

As for the largest leak in your paste, that's a false positive.
----------

More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=357#comment895

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to [EMAIL PROTECTED]

Reply via email to