mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dag Nygren <dag@newtech.fi>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Dag Nygren <dag@newtech.fi>,
	linux-kernel@vger.kernel.org, dag@newtech.fi
Subject: Re: 2.6.22.3 out of memory crash
Date: Mon, 01 Oct 2007 11:29:14 +0300	[thread overview]
Message-ID: <20071001082914.9A99B1160B@dag.newtech.fi> (raw)
In-Reply-To: Message from Nick Piggin <nickpiggin@yahoo.com.au>  of "Fri, 28 Sep 2007 07:40:18 +1000." <200709280740.18641.nickpiggin@yahoo.com.au>

> On Thursday 20 September 2007 16:56, Dag Nygren wrote:
> > Hi,
> >
> > I have the kview zoom function mapped to the scrollwheel
> > with ctrl.
> > Now my wife found out and watching our photos wanted
> > to zoom out a bit. Then she just rotated the scrollwheel a lot
> > and expected the zoom to happen. What did happen was that
> > as the there was no apparent response she tried again, and again.
> >
> > Finally the box probably was out of swap space (2GB RAM) and crashed
> > miserably.
> >
> > This is not the expected behavior from a Linux box using a graphics
> > viewer and I now wonder if there is something I can do about it?
> > Kernel parameters?
> > Kview patch?
> > New wife ;-)
> >
> > Best
> > Dag
> 
> 
> If the app has used up all memory, then there is not a great deal
> that the kernel can do about it.
> 
> The oom-killer ideally I suppose should terminate your kview process
> and the machine should continue normally after a fashion. How did
> it actually die? Any kernel messages?

Thanks for responding to this.

No messages.

Behaved like it was randomly killing other processes?? It was actually still
swapping furiously when I reset the machine (at least the hard disk LED was 
blinking), this after some 10 minutes or so.

At that time the whole desktop had died, also some other processes.

I would also like it to kill the offending process, not others if it can
be avoided.

Is the behavior of the OOM killer configurable? I might have it wrong.

I now set the ulimit -v (max virtual memory) to 512MB in hope of this
protecting my system, but this might get me into trouble when using gimp etc.

Best
Dag


      reply	other threads:[~2007-10-01  8:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-20  6:56 Dag Nygren
2007-09-27 21:40 ` Nick Piggin
2007-10-01  8:29   ` Dag Nygren [this message]

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=20071001082914.9A99B1160B@dag.newtech.fi \
    --to=dag@newtech.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®