dhdev at gmx.de
Thu Jan 4 18:08:23 GMT 2007
On Thursday 04 January 2007 16:49, Lubos Lunak wrote:
> On Sunday 17 December 2006 23:47, Thiago Macieira wrote:
> > John Tapsell wrote:
> > >Hey all,
> > >
> > > I am having a terrible time with memory usage. KSysguard takes up
> > >22MB of real memory for just showing the process list.
> > >
> > > I've ran valgrind's massif tool to try to find out what's using
> > >memory, but there's nothing specific that I can pin down.
> > >
> > > Any ideas why it takes up so much memory?
> It does not really. Not more than comparable KDE applications, at least.
> > How much of those 22 MB are the size of the shareable code from Qt
> > (core, ui, d-bus, svg, xml), KDE core and ui?
> > Measure how much memory you had free before running ksysguard and how
> > much you have now. See Luboš Luňák's somewhat recent blog on measuring
> > memory consumption for information on how to do it. (Or he can post a
> > reply here too...)
> Yes. Sorry it took a while, but there was this Xmas thingy, not reading
> mails and then reading them, and so on, and it also took a while to
> http://ktown.kde.org/~seli/memory/ (the analysis thing).
> Comments and whatever are welcome, I don't know if it's actually
> understandable and usable ;)
> (I'd even move it to some wiki if I wasn't
> afraid people would ruin it with clueless changes).
In that case the page can be "protected". Protected pages can only be
changed by a specific group (e.g. sysops). (This means ACLs for groups are
possible, but not for specific users (*) )
(*) without using extensions
More information about the kde-core-devel