| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 13 Dec 2014 12:26:35 -0300 From: Arnaldo Carvalho de Melo <acme@...nel.org> To: Markus Trippelsdorf <markus@...ppelsdorf.de> Cc: linux-kernel@...r.kernel.org, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...hat.com> Subject: Re: "perf top -g" leaking ~300MB per second. Em Sat, Dec 13, 2014 at 10:03:31AM +0100, Markus Trippelsdorf escreveu: > On 2014.12.13 at 09:48 +0100, Markus Trippelsdorf wrote: > > Running "perf top -g" built from current Linus tree apparently leaks > > ~300MB of memory every second an my machine. > > Hmm, this is a much older problem. I just noticed this the first time > today. > To reproduce: Compile some application in the background (make -j4 in my > case) and run "perf top -g". Perf will continue to accumulate memory > until the system starts to swap and the OOM killer eventually kicks in. Yeap, longstanding problem, try minimizing the problem using a lower frequency. The callchain code was done initially for 'report' and when I made 'top' reuse the hist_entry code allowing 'top' to collect callchains was too easy, but then we need to go thru the callchain/hists/hist_entry code to make sure that they don't leak, will try to do it... - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists