From: Boris Kurktchiev <techstuff@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Posible memory leak!?
Date: Tue, 13 May 2003 14:17:11 -0400 [thread overview]
Message-ID: <200305131417.11361.techstuff@gmx.net> (raw)
In-Reply-To: <200305131158.h4DBw2u30860@Port.imtp.ilyichevsk.odessa.ua>
On Tuesday May 13 2003 8:04 am, Denis Vlasenko wrote:
> On 12 May 2003 14:17, Boris Kurktchiev wrote:
> > I forgot to add that if I leave the machine long enough on (2-3 days)
> > the RAM usage goes down to like the normal 5/6% BUT the swap is
> > totaly used up with maybe like 5/6% left free.
> > Also, I forgot to attach my kernel config in case it helped,, so here
> > it is
>
> Instead of describing your problem at length just show top
> and various cat /proc/* output
> --
> vda
oh yeah and also if I turn swap off and leave the machine one besides the fact
that RAM usage does not go below 50% apps start dying from OOM (out of
memory) problems (even if there is more RAM free).
next prev parent reply other threads:[~2003-05-13 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 6:29 [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-10 7:38 ` Muli Ben-Yehuda
2003-05-12 3:26 ` Chris Friesen
2003-05-12 3:32 ` Doug McNaught
2003-05-12 3:42 ` Posible memory leak!? Boris Kurktchiev
2003-05-12 11:17 ` Boris Kurktchiev
[not found] ` <200305131158.h4DBw2u30860@Port.imtp.ilyichevsk.odessa.ua>
2003-05-13 18:17 ` Boris Kurktchiev [this message]
2003-05-12 18:06 ` Greg KH
2003-05-12 4:33 ` [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-12 13:23 ` Doug McNaught
2003-05-12 14:07 ` Chris Friesen
2003-05-12 3:53 ` Frank Cusack
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 18:15 Posible memory leak!? Boris Kurktchiev
2003-05-14 6:56 ` Denis Vlasenko
2003-05-14 14:12 ` Boris Kurktchiev
2003-05-15 5:51 ` Denis Vlasenko
2003-05-15 14:24 ` Boris Kurktchiev
2003-05-16 8:48 ` Denis Vlasenko
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=200305131417.11361.techstuff@gmx.net \
--to=techstuff@gmx.net \
--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 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.