Using fluxbox, I've had my laptop running for a few days, around 5 say. I have been using Konq as a web browser, with multiple windows open, say 7. I have half a gig of memory in this thing and it was pretty much all used up.
Now, either fluxbox has a good memory leak in it, or kdeinit does. I think kdeinit isn't letting go once it's been started. Even if I kill it off, it doesn't seem to free the memory up.
What would people say about this? See how there are so many kdeinit instances, and the size is from 10.5meg down. Certainly adds up!

2162 at 9 0 10388 10M 9280 S 0.0 2.0 0:00 kdeinit
2170 at 9 0 9464 9460 8596 S 0.0 1.9 0:00 kdeinit
2229 at 9 0 8472 8468 7744 S 0.0 1.7 0:00 kdeinit
2222 at 9 0 8356 8352 7744 S 0.0 1.6 0:00 kdeinit
2179 at 9 0 8352 8348 7780 S 0.0 1.6 0:00 kdeinit
2269 at 9 0 8348 8344 7744 S 0.0 1.6 0:00 kdeinit
2160 at 9 0 8268 8264 7756 S 0.0 1.6 0:00 kdeinit
2226 at 9 0 8228 8224 7720 S 0.0 1.6 0:00 kdeinit
2228 at 9 0 8228 8224 7720 S 0.0 1.6 0:00 kdeinit
2261 at 9 0 8220 8216 7712 S 0.0 1.6 0:00 kdeinit
2263 at 9 0 8208 8204 7700 S 0.0 1.6 0:00 kdeinit
2264 at 9 0 8208 8204 7700 S 0.0 1.6 0:00 kdeinit
2265 at 9 0 8208 8204 7700 S 0.0 1.6 0:00 kdeinit
2266 at 9 0 8208 8204 7700 S 0.0 1.6 0:00 kdeinit
2268 at 9 0 8208 8204 7700 S 0.0 1.6 0:00 kdeinit
2270 at 9 0 8208 8204 7700 S 0.0 1.6 0:00 kdeinit
2267 at 9 0 8204 8200 7700 S 0.0 1.6 0:00 kdeinit
2271 at 9 0 8204 8200 7700 S 0.0 1.6 0:00 kdeinit
2203 at 9 0 7692 7688 7288 S 0.0 1.5 0:00 kdeinit
2157 at 9 0 7344 7340 6996 S 0.0 1.4 0:00 kdeinit
2154 at 9 0 6848 6844 6628 S 0.0 1.3 0:00 kdeinit
2172 at 9 0 5320 5316 4360 S 0.0 1.0 0:00 kdesud

Remember to subtract off the SHARE value for all of those -- RSS includes the memory shared between processes.

Also do a cat /proc/meminfo - I bet you will find that a lot of memory is taken up by buffers and cache which is perfectly normal.

ok, I know that I am bombarding all threads with this, but I think that we have come upon an issue which needs to be addressed. kdeinit has some mem leak to it

Are you going to just bring up old threads to say kdinit is a problem or give any helpful advice to solving the problem? To me its not a memory leak or anything, KDE is just a resource hog. I'd recommend just using another desktop/window manager if their processes are slowing your machine down. But if it was and most of these threads are almost a year old, etc, it might have been a problem but hasn't been brought up recently so if it was some sort of bug of kdinit processes not dying off, then its been fixed in recent releases of KDE.

tricky,

I expected this kind of reply from you, knowing your preference for WMs over DEs (particularly KDE). But franky I don't care about your preferences, and have my own, and also have a problem with this kdeinit thing. I don't think that it is a matter of it being a resource hog, since it does not act lke one while I am using it. The matter does not lie with kdeinit processes dying off since I can see why they should be active (kicker is still running while nothing else is, and so is the kde window manager), rather with these processes absorbing more and more memory while the system is idle.

The only good point you make here is that this may have been fixed in later versions of KDE, this may be possible since I am using kde 3.0 that came originally with RH 8.0. I will upgrade it this weekend and see if it will make a difference.

I wish I could give some advice to solve the problem, I am seraching the web high and low to see if there are any solutions. I was hoping that some more knowledgeable people have had similar experiences and can point me in the right direction.

But rest assured that if I stumble upon a solution, or find that 3.1 addresses this problem, I will post it here first thing.

Cheers,
Vlad.

Actually you shouldn't assume this cause lately all I use is Gnome..

Regards.

Touche!!!