Created attachment 55217 [details] kded4 konsoleoutput-log Version: SVN (using KDE 4.5.90) OS: Linux Since 4.6 RC1 kded needs much systemmemory. after Systemstart its normal but an hour later it needs 700MiB, after 2h my system (2GiB of Sysmem) is not usable anymore. Reproducible: Always Steps to Reproduce: just start the System (new user created) Actual Results: kded takes more and more Systemmemory i dont know why it needs that much ram. if i kill kded4 and restart it the konsoleoutput is attached. it i can do anything please tell me
If this is reproducible, please try disabling some of the kded4 services in System Settings > System Administration > Startup and Shutdown > Service Manager to see if you can find the service that eats memory. Some services cannot be disabled graphically, so you might need to remove them from /usr/share/kde4/services/kded (or equivalent KDE directory). Please run kbuildsycoca4 and restart kded4 after each change.
Ok. I its because of "Power Management"
Can you please attach the running output of KDED (if you could valgrind it it would be really awesome), and tell me if you are doing something power management-related?
the konsoleoutput "kded4 2> $HOME/kded.log" is attached already (its a 20min log) i can ad a longer one if you need. i dont know valgrind but you can tell me how i have to use it and i will do. no. my laptop is on AC-power and i dont do anything else then start my computer (In reply to comment #3) > Can you please attach the running output of KDED (if you could valgrind it it > would be really awesome), and tell me if you are doing something power > management-related?
Created attachment 55249 [details] valegrind logs attached the "valgrind --tool=memcheck --leak-check=full --show-reachable=yes --leak-check=full kded4" logs. 1 with all kded services and the other only with powermanagement enabled
*back again* power management service is offline but kded4 starts to eat again. so its not the only service. but i cant make out the second one. can it have some relationship with "polkitd" who have 670MB(and more) sysmem? (its my second memleak-programm :s)
Thanks for the provided documents: what is sure is that power management is not taking part in the madness, from what Valgrind says. I suggest you to enable KDebug output (run kdebugdialog in a terminal and enable all the outputs), and log kded4's run. It will (hopefully) give some more infos. About polkitd, that's rather scary... I doubt it is related as no polkit-related service is actually running in KDED. I'm starting to fear that some things are leaked in the new brightness handler using KAuth, but again, you're not changing brightness at all. Try investigating the polkitd bug with Polkit developers, maybe it could give us some hints.
Created attachment 55354 [details] crashlog + runtime-log last days i have tested around a little bit. i was wrong. the sysmem usage go only higher if i activate that power thing in the systemsettings. polkitd starts to use that much sysmem too, only if Power Management is activated. polkitd uses additional CPU time with active Power Management (10-15%) and goes up to 20-25% + more sysmem usage if i change bringhtness. while deactivating from "Power Management" kded crashed, maybe there is some info in the crashlog too. its attached
Ouch. This log is pretty clear, and the problem is where I thought it was. Thank you very much for the detailed report, I wish all bug reports were like yours :)
One more question: when you recorded the log, were you changing brightness at all? Could you please post a kded4 log when you change the brightness, and one when you don't?
Created attachment 55386 [details] brightnes test logs (In reply to comment #10) > One more question: when you recorded the log, were you changing brightness at > all? Could you please post a kded4 log when you change the brightness, and one > when you don't? Yep, i had changed it. :) here are logs with and without changing (if they are to short i can log longer tomorrow.)
Unfortunately I am totally unable to reproduce this bug as of today... Let's try to solve the issue you are having with KAuth not working first. Are you installing KDE in a different prefix than /usr?
No, its in /usr ↓ $ kde4-config --prefix /usr
today i have startet my Laptop without the battery and kded works normal. then while running i take the battery in and it starts to eat. next i removed the battery again and it stops.
Interesting. Mind attaching kded4's output during the situation you described?
Created attachment 56059 [details] the kded4 + battery valgrind-log the Log. First i have started kded4, wait a little bit. next i set in the battery and wait another time and at last i removed the battery.
Dario, what is the status of this bug? We are still getting reports that kded4 massively leaks memory when Power Management kded module is enabled (see bug 271934, bug 206317 comment #56).
*** This bug has been marked as a duplicate of bug 271934 ***