Summary: | cache-limit for wallpapers does not work | ||
---|---|---|---|
Product: | [Unmaintained] 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: | ||
Sentry Crash Report: |
Description
S. Burmeister
2005-02-05 10:11:37 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. 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. 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. *** Bug 110873 has been marked as a duplicate of this bug. *** Does the problem still exist with KE 3.5? KDesktop's cache works just fine, probably X bug. Bug closed. Kdesktop is no more mantained. |