From: Michael Raskin <a1d23ab4@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc1-mm1+ memory problem
Date: Mon, 20 Nov 2006 21:18:20 +0300 [thread overview]
Message-ID: <4561F16C.1060205@mail.ru> (raw)
In-Reply-To: <45614A95.6090102@mail.ru>
Michael Raskin wrote:
> Short description: when X is loaded (maybe any heavy application is
> sufficient, but I don't use anything heavy in console), 'free' says used
> memory is growing.
>
Tried driver vesa. Leak still exists.
About leak size: with dri, xscreensaver, and nothing loaded while true;
do free >>free.log; sleep 1; done
shows ~100KB/s.
next prev parent reply other threads:[~2006-11-20 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 6:26 2.6.19-rc1-mm1+ memory problem Michael Raskin
2006-11-20 18:18 ` Michael Raskin [this message]
2006-11-21 8:37 ` Andrew Morton
[not found] ` <4563485B.3050801@mail.ru>
2006-11-21 19:45 ` Andrew Morton
2006-11-21 21:18 ` Michael Raskin
2006-11-24 13:23 ` Michael Raskin
2006-11-24 23:07 ` Michael Raskin
2006-11-25 19:03 ` Andrew Morton
2006-11-25 21:53 ` Michael Raskin
2006-11-29 4:29 ` 2.6.19-rc6-mm2 is ok (2.6.19-rc1-mm1+ memory problem) Michael Raskin
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=4561F16C.1060205@mail.ru \
--to=a1d23ab4@mail.ru \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox