Description: After upgrading from kdebase-3.5.0 to 3.5.0-r1 these days kdesktop started leaking memory. After KDE initilization kdesktop consumes about 20MB of RAM after 12h it consumes about 50MB and after 2 days I had it at 170MB (according to top)! I used kdebase-3.5.0 for several weeks without this specific problem. I can manually kill and launch kdesktop without restarting the whole KDE session, which frees the allocated memory, but the behaviour is always the same. Reproducible: always (at least on my system). Build Date & Platform: Thu Jan 05 2006 13:51:33 GMT+0100, AthlonXP, Gentoo 2005.1
My kdestop has been running 7 days: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND caleb 6119 0.0 2.6 34664 24256 ? S Jan04 0:19 kdesktop I'd say something else is going on. Are you sure it's a leak? You can always run it through valgrind and see what it says.
Created attachment 76826 [details] valgrind log of kdesktip run
Caleb, I attached a valgrind log as you suggested. Unfortunately I can't make any sense of it... I'm not much of a programmer... Alex!!
The log just says there is no memleak.
Hmm, still the problem remains... what else could it be. This is really annoying... Alex!!!
Might be https://bugs.kde.org/show_bug.cgi?id=98597 or https://bugs.kde.org/show_bug.cgi?id=110873 Alexander, does turning off wallpapers help you?
(In reply to comment #6) > Might be > > https://bugs.kde.org/show_bug.cgi?id=98597 > > or > > https://bugs.kde.org/show_bug.cgi?id=110873 > > > Alexander, does turning off wallpapers help you? > Looks good. I set the KDE background to plain color and made these ps snapshots every 15 minutes: runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:03 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:03 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:03 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:03 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:03 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:03 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S 20:56 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:04 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:05 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:05 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:05 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:05 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:05 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:05 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop runge 22014 0.0 1.4 28064 15320 pts/1 S May07 0:06 kdesktop So problem lies within kdesktop's caching routine, right!? Now, how can I live without my wallpapers ;-P Anyway, thanks for the hint, Alex!!!
(In reply to comment #7) > Now, how can I live without my wallpapers ;-P Well, stay with your top favourite wallpaper for now. Please follow the upstream bugs.
um, missed to resolve
