From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Milos Jakovljevic <sukijaki@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime.
Date: Fri, 16 Nov 2012 10:34:00 -0800 [thread overview]
Message-ID: <50A68718.3070002@linux.vnet.ibm.com> (raw)
In-Reply-To: <1353021103.6409.31.camel@c2d-desktop.mypicture.info>
On 11/15/2012 03:11 PM, Milos Jakovljevic wrote:
> Or maybe, it is just some problem with nvidia blob and 3.7 kernel
> loosing VM_RELEASE (in a blob's mmap.c it was replaced with
> VM_DONTEXPAND | VM_DONTDUMP ). - or maybe I'm just saying nonsense
> here.
I'm using Intel graphics, so it's not nvidia related for me, at least.
I've been recording a bunch of gunk from /proc once a minute for the
past 16 hours or so. I've grepped some of it in to a log file (but I've
got a *LOT* more than this):
http://sr71.net/~dave/linux/leak-20121113/log.1353087988.txt.gz
>From meminfo, it shows MemFree/Buffers/Cached/AnonPages/Slab/PageTables,
and their sum. That should capture _most_ of the memory use on the
system, and if we see that sum going down, it's probably a sign of the
leak, especially when we see a trend over a long period. The file is in
roughly this format, if anyone cares:
<nr/date> <meminfo fields> sums: <sum fields> <delta>
The system in question is my laptop. What I can tell is that it doesn't
leak much when I'm not using it. But, it's leaking pretty steadily
since I started using the system today (~6am in the logs). It
_averages_ leaking about 400kB/minute when idle and almost 9MB/minute
when in active use.
I've tried to provoke the leak doing specific things like large
downloads, kernel compiles, watching video, alloc'ing a bunch of
transparent huge pages, then exiting... No smoking gun so far.
Anybody have ideas what to try next or want to poke holes in my
statistics? :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-11-16 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-50181-27@https.bugzilla.kernel.org/>
2012-11-13 22:03 ` [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime Andrew Morton
2012-11-13 23:04 ` Milos Jakovljevic
2012-11-15 14:05 ` Milos Jakovljevic
2012-11-15 22:12 ` Andrew Morton
2012-11-15 23:11 ` Milos Jakovljevic
2012-11-16 18:34 ` Dave Hansen [this message]
2012-11-16 18:46 ` Milos Jakovljevic
2012-11-16 19:15 ` Andrew Morton
2012-11-16 23:59 ` Dave Hansen
2012-11-17 23:08 ` 3.7-rc6 memory accounting problem (manifests like a memory leak) Dave Hansen
2012-11-19 16:44 ` [Bug 50181] New: Memory usage doubles after more then 20 hours of uptime Dave Hansen
2012-11-16 2:51 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50A68718.3070002@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sukijaki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.