Trying to use Digikam for Windows was proven to be impossible. Immediately after opening the software for the first time, all the CPU cores were taken my WMI provider service processes. The load did come off, a few minutes after closing every Digikam window. This seems to be posted already as a Amarok bug, which it certainly is not: https://bugs.kde.org/show_bug.cgi?id=306994 With Digikam, there however spawned several WPI processes making even a multi-core system unresponsible. Reproducible: Always Steps to Reproduce: 1. Install the current stable Digikam for Windows. 2. Launch it. Actual Results: The system could not be used due to extremely high CPU load on every CPU core. Expected Results: I should have been able to use Digikam. The Amarok developers requested some information on hard disk drives, so here are the controllers and the devices attached to them. - Intel ICH9 south bridge's serial ata controller - Samsung SSD 830 - Western Digital WDC6400AAKS HDD - Samsung HD154UI HDD - Hitachi-LG DVD-RW drive - JMicron JMB36X serial ata controller - Samsung HD642JJ HDD - a no-name USB card reader
Can you please try to detach the card reader? I guess the card-reader is a multi-format card reader?
Yes, of course. The problem would not disappear by starting the computer without the card reader, the WmiPrvSE.exe processes still take all the CPU time available for a long period of time (might do so forever, as well). The card-reader is a 7-in-1 model, however it seems to be unrelated.
While preparing the KMyMoney installer I observed the same problem in KDE 4.8.5. Basically the file selector dialog was really slow and hugging the CPU. I remember that I asked about this on #kde-windows and got the answer (from TheOneRing) that this is a known issue of the WMI solid backend which needs to be completely rewritten. So I disabled the WMI backend in the package.
There will be a new solid backend uploaded in the coming days, which will fix this issue.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.