Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20609 - [kshutdown] memleak with KDE 4.5
Attached to Project:
Arch Linux
Opened by OldShatterhand (OldShatterhand) - Wednesday, 25 August 2010, 21:21 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 29 August 2010, 09:03 GMT
Opened by OldShatterhand (OldShatterhand) - Wednesday, 25 August 2010, 21:21 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 29 August 2010, 09:03 GMT
|
DetailsDescription:
After the update of Kde to version 4.5 i got an "temporary" memleak at every start of Kshutdown. This memleak fills my hole ram (2 GB) and my half swap (1GB/2GB). This takes a half to a minute. After KShutdown has started the memleak goes away and everything is normal again. Additional info: * package version(s) KShutdown Version 2.0 Beta 9 Steps to reproduce: Start KShutdown under Kde 4.5 |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Sunday, 29 August 2010, 09:03 GMT
Reason for closing: Fixed
Additional comments about closing: beta11
Sunday, 29 August 2010, 09:03 GMT
Reason for closing: Fixed
Additional comments about closing: beta11
i've made a new "discovery". Today Kshutdown first produced no memleak. Then I started Kontact (with Kmail). Restarting Kshutdown produces the memleak. I turned of Kontact: KShutdown starts normaly.But after the third try kshutdown again produced the memleak at every start... no idea why but it happens. I hope this will help you to locate and fix the bug.
MfG OldShatterhand