Bug 98597

Summary:	cache-limit for wallpapers does not work
Product:	kdesktop	Reporter:	S. Burmeister <sven.burmeister>
Component:	wallpaper	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	CLOSED WORKSFORME
Severity:	normal	CC:	finex, l.lunak, p0
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description S. Burmeister 2005-02-05 10:11:37 UTC

Version:            (using KDE KDE 3.3.91)
Installed from:    SuSE RPMs
OS:                Linux

This might be similar to bug 10853. I have set slideshow to change my desktop-background every minute. I gave it a directory with ~800 images in it most have a resolution 1024x768.

Every time the picture is changed, X's memory-usage goes up by ~300-600 kb, sometimes even 2 MB.

I have set the cache-limit to 2048 kb, so this should not happen, or is a X.org issue.

Comment 1 S. Burmeister 2005-02-05 11:06:54 UTC

I am not familiar with the random function to determine the next wallpaper. I notice that not every new wallpaper causes the memory usage to increase, yet most do.
This can be due to the new wallpaper coming from cache, in case random means that a picture can be displayed twice even though not all images have already been displayed once. Otherwise it might be related to the picture-file.

Another thing I notice, is that when I have all windows minimised but the ksysguard window, then wait some time till some new wallpapers have passed and move the ksysguard window, X's memory usage drops by 2 MB. Yet, next time the wallpaper changes it increases by 2MB + x.

Comment 2 S. Burmeister 2005-02-05 11:12:01 UTC

Starting with 36MB memory usage at the beginning of a session, after 150 minutes X's memory consumption is at 97 MB. The difference is exactly what one would expect for 150 minutes, a picture each, increasing memory usage by 300-400 kb each.

Comment 3 Stephan Kulow 2005-02-07 18:56:28 UTC

my X session runs since 83 days and every 4 minutes a new wallpaper is set and X's memory has 160MB - I have my doubts this is a kdesktop bug. We had this before and back then it was specific to some X drivers that didn't destruct the pixmaps.

Comment 4 Kurt Hindenburg 2005-12-18 06:37:37 UTC

*** Bug 110873 has been marked as a duplicate of this bug. ***

Comment 5 Philip Rodrigues 2006-08-07 20:59:07 UTC

Does the problem still exist with KE 3.5?

Comment 6 Lubos Lunak 2006-08-25 11:59:38 UTC

KDesktop's cache works just fine, probably X bug.

Comment 7 FiNeX 2009-01-02 20:29:58 UTC

Bug closed. Kdesktop is no more mantained.