[awesome bugs] #357 - git-awesome leaks memory
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been re-opened: FS#357 - git-awesome leaks memory User who did this - Julien Danjou (jd) More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Julien Danjou (jd) -- No leak here. Can you check with valgrind ? Some people were talking about cairo leaking. This people should precise which version and on which OS. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment894 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]
[awesome bugs] #357 - git-awesome leaks memory
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=detailstask_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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Julien Danjou (jd) -- Why _your_ valgrind? And why can't I see this? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment896 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]
[awesome bugs] #357 - git-awesome leaks memory
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) -- I should note that the bug reporter doesn't suffer from this leak it seems. So it's some other leak. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment899 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Julien Danjou (jd) -- The original bug as already been close. There's only the title that matches… -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment900 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]
[awesome bugs] #357 - git-awesome leaks memory
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#357 - git-awesome leaks memory User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 4f1273794b2844455d8df1ba9e29de472f3d784e Author: Julien Danjou [EMAIL PROTECTED] Date: Fri Oct 24 18:53:47 2008 +0200 mouse: fix button delete We need to unref Lua functions. Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Julien Danjou (jd) -- Ok, so now we should try to know how to debug Lua leaks. ;) -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment834 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - calmar (calmar) -- I uncommented everything, unless 'awful' and I was still able to increase the count also after a collect. So must be something in awful it seems. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment835 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Julien Danjou (jd) -- Adding --show-reachable to valgrind show a huge memory consuption in the Lua tasklist code. Trying to get why… -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment836 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Julien Danjou (jd) -- Hum, a quick look with valgrind did not reveal anything suspicious so far. Any bigger chance on your side? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment824 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - Hannes Schulz (hannes) -- I'll try to figure it out, but I'm not quite proficient regarding valgrind. The problem, however, persists, I'm back to 18% RAM usage now (htop). -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment827 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - calmar (calmar) -- I can at least about confirm it. like shown on the screenshot: http://www.calmar.ws/tmp/013-Fri-screen.png (~41%) I don't use ultimate latest git, but I try also to dig it down then. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment830 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]
[awesome bugs] #357 - git-awesome leaks memory
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 - calmar (calmar) -- it seems it's possible to increase the memory by opening/closing clients. Gimp or just terminals. Like opening 20 and closing them again etc. It seems. http://www.calmar.ws/tmp/typescript - pmap `pidof awesome` -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment831 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]
