[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

[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

[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

[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:

[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.

[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

[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

[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

[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

[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… --

[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? --

[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

[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

[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