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