Summary: | plasma keeps copy jobs in plasma-desktop-appletsrc and thus grows the config file endlessly causing slow plasma launch | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | S. Burmeister <sven.burmeister> |
Component: | notifications | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | asraniel, cincaipatron, lydia, notmart |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
S. Burmeister
2009-08-08 11:14:52 UTC
Another note: With my ~200kb config file plasma used more thatn 100MB RAM according to the process list. With a clean config and the same applets it uses only 50MB. I can confirm this bug (and I happen to use openSUSE rpms too). The [ExtenderItems] for completed jobs are saved into plasma-desktop-appletsrc. Sometimes, this is accompiened by the [PopupApplet] too. This bug happens even with simple browsing activities using Konqueror or Dolphin+kio_sftp. ================================================= [Containments][3][Applets][11][Configuration][ExtenderItems][63] extenderTitle=Job canceled by user. label0=ftp://ftp.ncbi.nih.gov/blast/db label1= labelName0=File labelName1= [Containments][3][Applets][11][PopupApplet] DialogHeight=59 DialogWidth=416 ================================================= yeah, can confirm here on trunk build, will take a look SVN commit 1014430 by mart: don't write the extenderitem config after it was destroyed, mmkay? will backport BUG:203058 M +13 -2 jobwidget.cpp M +3 -0 jobwidget.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1014430 Does this take care of those config files which do already have lots of those items in them, i.e. clean them up? nope, would be quite messy code for a single use Well, now you leave all the 4.3.0 users with a messy plasma config file which might even cause a slow KDE start-up. I'll try to get this on the mailingslists etc. in order for people to fix it on their own. Leaving all those items in there is not really a solution but just the end of adding errors. Marco, couldn't a kconf_update script be used in this event? It should quite easy to recognize and delete completed jobs. |