From: Helge Hafting <helgehaf@aitel.hist.no>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange behavior in out-of-memory situation
Date: Thu, 24 Apr 2003 21:02:48 +0200 [thread overview]
Message-ID: <20030424190248.GA2766@hh.idb.hist.no> (raw)
In-Reply-To: <3EA83396.4040904@techsource.com>
On Thu, Apr 24, 2003 at 02:57:26PM -0400, Timothy Miller wrote:
> I'm using Red Hat kernel 2.4.18-26.7.x.
>
> I ran a program which is trying to suck up all of memory. I would like
> to kill the process, but "top", "vmstat", and "ps" all hang when I try
> to use them. Also, pressing ctrl-c in the terminal where I can the
> program won't kill it.
>
> To an extent, however, the system was still usable, albeit EXTREMELY
> unresponsive. Eventually, the program dumped core, and everything
> returned to norma.
>
> Is this a known problem?
Your system seems to be in normal working order. There is no problem here.
A program using up all memory _will_ make the machine very unresponsive
as everything goes into swap (or discards all executable code for
those who think they can fool the system by not having swap).
You may indeed be unable to run other programs like top, because
there aren't enough memory left to run them. Your program probably
dumped core when it ran the system completely out of memory and
trigged the Out-Of-Memory killer.
The only unusual here is that ctrl+c didn't work, but some
programs block that signal. Perhaps your program does too.
You can use ulimit if you don't want your machine to become
sluggish. The effect is that your memory eater will be killed
earlier, before it uses up so much memory that nothing else
will run.
Helge Hafting
next prev parent reply other threads:[~2003-04-24 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 18:57 Strange behavior in out-of-memory situation Timothy Miller
2003-04-24 19:02 ` Helge Hafting [this message]
2003-04-24 19:26 ` Timothy Miller
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=20030424190248.GA2766@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).