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

List:       kde-devel
Subject:    Re: Dealing with a memory leak
From:       Ian Wadham <iandw.au () gmail ! com>
Date:       2009-11-24 22:32:27
Message-ID: 200911250932.27415.iandw.au () gmail ! com
[Download RAW message or body]

On Wednesday 25 November 2009 2:10:51 am Thomas Lübking wrote:
> Am Tuesday 24 November 2009 schrieb Anne Wilson:
> > I'd be interested to hear other opinions of this - it sounds a better
> >  option unless there are penalties :-)
> 
> a) you need to ensure that your DM (KDM iirc does) interprets ~/.bashrc
> b) this would likely cause trouble on things like games - and iff applied
>  on kdeinit4... eww :-\
> 
AFAIK all KDE Games are well-behaved in this regard.  Large 3-D games
might require large memory limits.  I would hope that, if you set the limit
to about a third to a half your total physical-memory, KDE would start up
OK.  But if you would like some more FUD have a look at the threads on
"What the ...? Virtuoso eats memory like mad" and "Akonadi and Kmail
problems".  It appears that we will soon require a fully-fledged relational
database manager in order to read mail, manage contacts and index text.

Speaking personally, this seems to me like recruiting elephants to do
neurosurgery.  I say that as one who pioneered the use of RDBMS in
distributed Unix systems in 1987-98.  We eventually had 1000 users,
20 hosts and 10 databases, managing about 100,000 properties and
about 500,000 rental and loan clients for our State Government.  I
have recently programmed a DB app for an organization with about
800 subscribing members, but that is about as small as I would like
to go with such heavy-duty technology.

> I'd rather just wrap the offending app into a convenience script, than
>  drawing the broadsword...
> 
In KDE 2 times, the computer opponent in one of the KDE Games, if you
configured maximum board size and difficulty, would go into a trance and
slowly bur surely paralyze your desktop, due to a memory leak.

I thought then, and still think, that KDE is rather vulnerable to a Denial of
Service attack, from which the "broadsword" (ulimit) offers protection.

Meanwhile, are you saying memory should be *unlimited* for KDE and all
its apps?  If so, what about the children in Africa with old PCs who are using 
Kubuntu?

All the best, Ian W.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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