<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>108326</bug_id>
          
          <creation_ts>2005-06-29 16:13:56 +0000</creation_ts>
          <short_desc>Huge memleaks in krootimage (at least with SVG slideshow)</short_desc>
          <delta_ts>2008-05-19 17:30:46 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>10</classification_id>
          <classification>Unmaintained</classification>
          <product>kdm</product>
          <component>krootimage</component>
          <version>unspecified</version>
          <rep_platform>openSUSE</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jo Schulze">jo</reporter>
          <assigned_to name="kdm bugs tracker">kdm-bugs-null</assigned_to>
          <cc>wildfox</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>354347</commentid>
    <comment_count>0</comment_count>
    <who name="Jo Schulze">jo</who>
    <bug_when>2005-06-29 16:13:56 +0000</bug_when>
    <thetext>Version:            (using KDE KDE 3.4.1)
Installed from:    SuSE RPMs
OS:                Linux

After upgrading to KDE3.4.1, I tweaked kdm to display 4 different *.svgz wallpapers in slideshow mode on our server (which provides httpd, cupsd, mail via exim, mysqld, NIS, nfs, sshd, proftpd and serves several LTSP terminals). Since it&apos;s a server, the propability that kdm will run for a long time because no one logs in directly is pretty high. Here is the backgroundrc:
Background Common]
CacheSize=99
CommonDesktop=true
Dock=true
Export=false
LimitCache=true

[Desktop0]
BackgroundMode=VerticalGradient
BlendBalance=100
BlendMode=NoBlending
ChangeInterval=60
Color1=0,0,0
Color2=192,192,192
CurrentWallpaper=0
LastChange=1112890721
MinOptimizationDepth=1
MultiWallpaperMode=Random
Pattern=
Program=
ReverseBlending=false
UseSHM=true
Wallpaper=/opt/kde3/share/wallpapers/andes-venezolanos.svgz
WallpaperList=andes-venezolanos.svgz,aurora.svgz,here-gear.svgz,globe.svgz
WallpaperMode=Scaled

[FMSettings]
ItemTextBackground=invalid
NormalTextColor=0,0,0
ShadowEnabled=true
TextHeight=2
TextWidth=0
--eof

After that, I noticed that the whole machine became instable. Some services would die unexpectedly out of the blue, resulting in calls early in the morning: &quot;I can&apos;t print/mail/login/...&quot; I increased the loglevel and all these services were shutdown because of insufficient memory. Here is an example for mysqld:
Jun 29 12:17:19 holos kernel: Out of Memory: Killed process 7259 (mysqld-max).
Jun 29 12:27:36 holos kernel: Out of Memory: Killed process 10238 (mysqld-max).
Jun 29 12:27:36 holos kernel: Out of Memory: Killed process 10243 (mysqld-max).
Jun 29 12:27:36 holos kernel: Out of Memory: Killed process 10244 (mysqld-max).
Jun 29 12:36:57 holos kernel: Out of Memory: Killed process 10276 (mysqld-max).
Jun 29 12:36:57 holos kernel: Out of Memory: Killed process 10281 (mysqld-max).
Jun 29 12:36:57 holos kernel: Out of Memory: Killed process 10282 (mysqld-max).
Jun 29 12:38:09 holos kernel: Out of Memory: Killed process 10343 (mysqld-max).
--eof

I also noticed in the systat logs that the machine had strange swap actions at times where no one would actually work and no cronjob was active.

Well, today I found that one krootimage process alone occupied 48% of the memory (on a machine with 1GB phys. RAM and 0.5GB swap). Another was at 2nd place (systemwide) with 9%.

8-O

I think that&apos;s a bit too much for some eyecandy, eat up more memory than other services which are _really_ vital.
For now, I disabled the slideshow (logically, the memleak will be related to the slideshow mode, since displaying one picture for a long time shouldn&apos;t require any mem access once the data is loaded).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>355449</commentid>
    <comment_count>1</comment_count>
    <who name="Jo Schulze">jo</who>
    <bug_when>2005-07-05 02:26:02 +0000</bug_when>
    <thetext>Disableing the slideshow mode did the trick. The server is rock stable again.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>356378</commentid>
    <comment_count>2</comment_count>
    <who name="Oswald Buddenhagen">ossi</who>
    <bug_when>2005-07-08 19:23:56 +0000</bug_when>
    <thetext>hmm, on first sight it indeed looks like the svg loader would be leaking rocks. maybe niko can say more. calling file is kdebase/kcontrol/background/bgrender.cpp starting with line 300. that code looks pretty hackish in general ...
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>470285</commentid>
    <comment_count>3</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-09-16 08:54:54 +0000</bug_when>
    <thetext>Fixed in revision 584936 yesterday.
Oswald: Thanks for pointing it out.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>