From: Kestutis Kupciunas <kesha@soften.ktu.lt>
To: Linux-MM@kvack.org
Subject: oom - out of memory
Date: Mon, 20 Sep 1999 15:35:12 +0200 [thread overview]
Message-ID: <19990920153512.A20067@alna.lt> (raw)
hello, linux memory managers,
thing i am eager to clarify is oom, out of memory problem,
which doesn't work as it is supposed to (at least i think it
doesn't do the trick). Having the system fully utilizing all the
memory available on box and requesting more simply "hangs"
the box.
Going into more details: i have noticed this behavior
with all 2.[23].x kernels i have used (not sure about the previous series).
usually problem arises when manipulating LARGE sets of large images
under X (with gimp, imagemagick tools). as i open more images, naturally,
memory/swap usage grows, and when it grows to the bounds, keyboard stops
responding, screen stops repainting, hdd led's going crazy. all box
services stop responding - i'm unable to connect from remote box. *RESET* :(
this behavior isnt my box specific - i've vitnessed it happening on
a bunch of different intels as well. The only chracteristics that apply
to all those boxes are that all of them are x86.
but according to the oom() function, the pid which is requesting
memory when it's out, is beeing killed with a message.
i didnt find any message in logs later...
im not a 'kernel hacker', so maybe somebody could analyze the lifecycle
of linux-mm memory allocating up to the bounds and over?
or is there something i don't get right?
sorry for the messy english
regards,
ydum
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-09-20 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-20 13:35 Kestutis Kupciunas [this message]
1999-09-23 18:15 ` David Kulp
1999-09-25 14:31 ` Andrea Arcangeli
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=19990920153512.A20067@alna.lt \
--to=kesha@soften.ktu.lt \
--cc=Linux-MM@kvack.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