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

List:       kde-devel
Subject:    Re: KDE Application memory management
From:       "John Tapsell" <johnflux () gmail ! com>
Date:       2007-01-29 17:14:31
Message-ID: 43d8ce650701290914i65dd9b33ld3b8d86f95e71814 () mail ! gmail ! com
[Download RAW message or body]

Hi Sebastian,

  It's also worth using ksysguard from kde4 to look at the memory
usuage.  It will give you a better picture of what app is using what.

On 29/01/07, Sebastian Trüg <trueg@k3b.org> wrote:
> On Monday 29 January 2007 17:05:36 Lubos Lunak wrote:
> > On Monday 29 January 2007 16:49, Sebastian Trüg wrote:
> > > On Monday 29 January 2007 16:32:03 Lubos Lunak wrote:
> > > >  http://ktown.kde.org/~seli/memory/analysis.html . It's in the
> > > > application memory analysis intro.
> > >
> > > Hi Lubos,
> > >
> > > thanks for the hint. So the reason could be that I allocate many small
> > > pieces, right? Is there anything easy I can do against this? K3b keeps
> > > blocking memory it does not really use (or should not use).
> >
> >  That's also said in the document :). Not easily, especially if the
> > allocations are done by Qt (big project means a large number of files,
> > right?). You can of course help it also by reducing general memory usage
> of
> > K3b. But there's not that much to say without analysing K3b's memory
> usage.
>
> ok, thanks. :)
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
> <<
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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