[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: How to handle Out-of-Memory in Konqueror?
From:       George Staikos <staikos () kde ! org>
Date:       2004-02-27 3:33:18
Message-ID: 200402262233.18534.staikos () kde ! org
[Download RAW message or body]

On Thursday 26 February 2004 20:57, Jason Keirstead wrote:
> On February 25, 2004 09:47 am, Stefan Taferner wrote:
> > > Hmm...
> > > There are already 2 people complaining about the crash. At least one
> > > uses "ulimit -v", i.e. he is by purpose limiting the amount of virtual
> > > memory for each process.
> >
> > What I've meant: traditionally in Unix programs one does not care about
> > out of memory conditions. IMO the ulimit thing is to ensure a process
> > does not eat up all memory, knowing that those processes probably crash
> > when they hit the limit.
>
> Couldn't this problem be more easily subverted KDE-wide? I know under
> Windows when an application starts chewing memory, the OS itself warns the
> user of this fact and asks them if they want it closed. It's not left up to
> the application.r
>
> Couldn't we monitor KDE processes via kdeinit or a kded for their VM usage
> (a-la vmstat) and if it looks like it's getting out of hand, halt the
> process and pop up a confirmation dialog asking the user if they want to
> continue down their currently dangerous road?

  There's a kicker applet for doing that already.  It's been there since KDE 
2.0 I think.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/
[prev in list] [next in list] [prev in thread] [next in thread]