On Tue, 1 Jan 2013 23:54:16 +0800 Jianjun Mao <[email protected]> wrote:
> Don't think so. lua gc is simple and good enough. > I think may some resources allocated from lower library but forgot to > release after using... > That's the reason why did not make any difference to the memory usage in > top ? AFAIK releasing free memory back to the system is up to the allocator. That alone does not mean its a leak. How about trying valgrind? FWIW, I've seen my (git master + some patches) awesome eat 80MB after 1-2 days of uptime, now its at 13MB few hours after a restart. And yes, CPU usage has gone up for me, widgets on short timers are the cause (say 1s update time). The new widget layouts are more CPU-hungry, there is no solution yet :( lukash > > > On Tue, Jan 1, 2013 at 9:35 PM, Uli Schlachter <[email protected]> wrote: > > > Hi, > > > > On 01.01.2013 07:05, Jianjun Mao wrote: > > > 3.5 has memory leak? after 11 hours awesome grows to 70MB+ > > > > Nothing is impossible. I'm at 76MiB after an uptime of 27h. However, no > > idea > > what the memory usage was right after startup. Might also just be the lua > > garbage collector being slower than needed. Dunno. > > > > A quick-and-dirty experiment suggests that there was some garbage laying > > around: > > > > $ echo 'return collectgarbage("count")' | awesome-client > > double 39222.4 > > $ echo 'return collectgarbage("collect")' | awesome-client > > double 0 > > $ echo 'return collectgarbage("count")' | awesome-client > > double 23356.1 > > > > (This did not make any difference to the memory usage in top) > > > > Uli > > -- > > - He made himself, me nothing, you nothing out of the dust > > - Er machte sich mir nichts, dir nichts aus dem Staub > > > > -- > > To unsubscribe, send mail to [email protected]. > > > > > > -- > Jianjun Mao -- Blog <http://justmao.name> -- To unsubscribe, send mail to [email protected].
