[opensuse-kde] bluedevil causes kded4 to leak memory
Hello, On oS 13.1, KDE 4.14.4, bluedevil-2.1-22.2.x86_64, after resuming from suspend-to-RAM, kded4 starts leaking memory at the rate of a couple of MB/s, while it fills .xsession-errors-:0 with: Error response: "The name org.kde.bluedevilmonolithic was not provided by any .service files" and a backtrace indicates that it repeatedly calls BlueDevilDaemon::killMonolithic. kded4 does not respond to signals during this, and the only way to prevent it from consuming the entire RAM of the system is to kill it. Has anyone else seen this? -- Regards, Peter -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am 01.02.2015 um 10:16 schrieb auxsvr@gmail.com:
Hello,
On oS 13.1, KDE 4.14.4, bluedevil-2.1-22.2.x86_64, after resuming from suspend-to-RAM, kded4 starts leaking memory at the rate of a couple of MB/s, while it fills .xsession-errors-:0 with:
Error response: "The name org.kde.bluedevilmonolithic was not provided by any .service files"
and a backtrace indicates that it repeatedly calls BlueDevilDaemon::killMonolithic. kded4 does not respond to signals during this, and the only way to prevent it from consuming the entire RAM of the system is to kill it.
Has anyone else seen this? I can reproduce the issue on current Tumbleweed. Did you file a bugreport about that already? I made a heaptrack profile of the leak while it happened that I could attach to the report.
To stop the leak you can manually start a bluedevil-monolithic on the commandline (which kded will then find and kill and stop the loop) Br, Christoph -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 02 of February 2015 22:56:32 Christoph Obexer wrote:
I can reproduce the issue on current Tumbleweed. Did you file a bugreport about that already? I made a heaptrack profile of the leak while it happened that I could attach to the report.
One had already been filed, https://bugs.kde.org/show_bug.cgi?id=343682
To stop the leak you can manually start a bluedevil-monolithic on the commandline (which kded will then find and kill and stop the loop)
I disabled bluedevil in the services of kded to stop the leak. -- Regards, Peter -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (2)
-
auxsvr＠gmail.com -
Christoph Obexer