Re: Likely mem leak in 3.7

2012-12-01 Thread James Cloos
I've extensively tested 2844a48706e5 (tip at the time I compiled) for the last few days and have been unable to reproduce. This bug appears to be fixed. Thanks. -JimC -- James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6 -- To unsubscribe from this list: send the line unsubscribe

Re: Likely mem leak in 3.7

2012-11-17 Thread James Cloos
DR == David Rientjes rient...@google.com writes: I had to reboot to get some work done. In order to re-create the missing ram I had to use a btrfs fs for the temp files for a few emerge(1) runs. It seems that the ram which was used for the cache of those temp files is not recovered when the

Re: Likely mem leak in 3.7

2012-11-16 Thread David Rientjes
On Thu, 15 Nov 2012, James Cloos wrote: The kernel does not log anything relevant to this. Can you do the following as root: dmesg -c /dev/null echo m /proc/sysrq-trigger dmesg foo and send foo inline in your reply? Slabinfo gives some odd output. It seems to

Likely mem leak in 3.7

2012-11-15 Thread James Cloos
Starting with 3.7 rc1, my workstation seems to loose ram. Up until (and including) 3.6, used-(buffers+cached) was roughly the same as sum(rss) (taking shared into account). Now there is an approx 6G gap. When the box first starts, it is clearly less swappy than with = 3.6; I can't tell whether