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

List:       kde-devel
Subject:    Re: Dealing with a memory leak
From:       Anne Wilson <cannewilson () googlemail ! com>
Date:       2009-11-24 9:24:03
Message-ID: 200911240924.09959.cannewilson () googlemail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 23 November 2009 22:33:13 Ian Wadham wrote:
> On Monday 23 November 2009 8:28:30 pm Lubos Lunak wrote:
> > On Sunday 22 of November 2009, Anne Wilson wrote:
> > > Can you give me a bit more detail?  If it *is* nspluginviewer that
> > > triggers it, for instance, what do I need to do to set that limit?
> >
> >  Open Konsole, do 'ulimit -m 524288' (or whatever you consider good
> > limit) and run 'konqueror'. Not very convenient.
> 
> I believe you can also put the ulimit command in your $HOME/.bashrc file,
>  so as to catch any memory hog process any time.  It used to work years
>  ago, but it could be risky as a general policy nowadays (dunno).
> 
I'd be interested to hear other opinions of this - it sounds a better option 
unless there are penalties :-)

Anne
-- 
KDE Community Working Group
New to KDE4? - get help from http://userbase.kde.org

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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