<div dir="ltr">PLease remove me from your email list..<br><br>I am not the right person, so please please remove me..<br><br>Thanks<br><br><div class="gmail_quote">On Sun, Feb 3, 2013 at 4:06 AM, Sami V. Koskinen <span dir="ltr"><<a href="mailto:sami_koskinen@kolumbus.fi" target="_blank">sami_koskinen@kolumbus.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="https://bugs.kde.org/show_bug.cgi?id=314317" target="_blank">https://bugs.kde.org/show_bug.cgi?id=314317</a><br>
<br>
Bug ID: 314317<br>
Summary: WMI provider processes take all CPU and system is<br>
extemely unresponsible for several minutes, at least<br>
Classification: Unclassified<br>
Product: kde-windows<br>
Version: unspecified<br>
Platform: Other<br>
OS: MS Windows<br>
Status: UNCONFIRMED<br>
Severity: critical<br>
Priority: NOR<br>
Component: general<br>
Assignee: <a href="mailto:kde-windows@kde.org">kde-windows@kde.org</a><br>
Reporter: <a href="mailto:sami_koskinen@kolumbus.fi">sami_koskinen@kolumbus.fi</a><br>
<br>
Trying to use Digikam for Windows was proven to be impossible. Immediately<br>
after opening the software for the first time, all the CPU cores were taken my<br>
WMI provider service processes. The load did come off, a few minutes after<br>
closing every Digikam window.<br>
<br>
This seems to be posted already as a Amarok bug, which it certainly is not:<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=306994" target="_blank">https://bugs.kde.org/show_bug.cgi?id=306994</a><br>
<br>
With Digikam, there however spawned several WPI processes making even a<br>
multi-core system unresponsible.<br>
<br>
<br>
<br>
Reproducible: Always<br>
<br>
Steps to Reproduce:<br>
1. Install the current stable Digikam for Windows.<br>
2. Launch it.<br>
Actual Results:<br>
The system could not be used due to extremely high CPU load on every CPU core.<br>
<br>
Expected Results:<br>
I should have been able to use Digikam.<br>
<br>
The Amarok developers requested some information on hard disk drives, so here<br>
are the controllers and the devices attached to them.<br>
<br>
- Intel ICH9 south bridge's serial ata controller<br>
- Samsung SSD 830<br>
- Western Digital WDC6400AAKS HDD<br>
- Samsung HD154UI HDD<br>
- Hitachi-LG DVD-RW drive<br>
<br>
- JMicron JMB36X serial ata controller<br>
- Samsung HD642JJ HDD<br>
<br>
- a no-name USB card reader<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
_______________________________________________<br>
Kde-windows mailing list<br>
<a href="mailto:Kde-windows@kde.org">Kde-windows@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(136,136,136)"></span><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(136,136,136)">Regards,</span>
<span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(136,136,136)"><br><br>Faizan Ahmed Khan</span><br><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(136,136,136)"><br>
</span></div>
</div>