On Tuesday 26 July 2011 19:48:06 Andreas Roth wrote: > With the help of the amarok developers is found the piece of code, which > triggers this issue. In amarok/src/MediaDeviceCache.cpp, function > MediaDeviceCache::slotTimeout() calls Solid::Device::listFromType, which > does some dbus/udisks magic and this causes the trouble. I haven't gone > into the solid code to check what might be wrong there.
Well, I guess the real question is why does Amarok poll in the first place? libsolid is doing what it's supposed to do: if you query a list is asks the system for it (in that case udisks). So obviously if you constantly ask the system you get the system component always eating CPU. I would advise against having this kind of libsolid call triggered by a timer. libsolid provides the necessary signals to let you know when a new device appeared or disappeared. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud patron of KDE, http://www.kdab.com
signature.asc
Description: This is a digitally signed message part.
