Bug 306994

Summary:	[Windows] WMI Provider Host taking up a CPU-Core
Product:	[Unmaintained] solid	Reporter:	Fabian Korak <fabiank22>
Component:	libsolid-windows	Assignee:	Ralf Habacker <ralf.habacker>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	jr, matej, ralf.habacker, vonreth
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Fabian Korak 2012-09-18 18:36:44 UTC

Hello,

I'm running the latest 2.6-binaries provided for Windows on a Laptop running Windows 8 64-bit. After I start Amarok it just freezes and the Process WMI Provider Host starts taking up 25-50% of my CPU-Power (I'm running a dual-core i5 with HT enabled). Killing that process starts a "Amarok has crashed"-window, restarts the process and does nothing. Amarok stays frozen during all of this.

Greetings,
Fabian Korak

Comment 1 Matěj Laitl 2012-10-01 15:33:16 UTC

Patrick?

Comment 2 Hannah von Reth 2012-10-03 11:43:06 UTC

The problem is the solid backend, the used technology isn't fast enough that's why the wmi process takes so much cpu . But freezing is not expected.

I already started a new implementation but it will take some time.

I'm not sure but I got the felling that Amarok is polling somewhere all the devices which wont improve the performance.

But it would be interesting to see a list of your devices.
So cd/dvd devices and hard disks.

Comment 3 Matěj Laitl 2013-06-30 14:02:01 UTC

Reassigning to solid per Patrick's comment #2.

Comment 4 Jonathan Riddell 2015-03-11 19:10:05 UTC

This bug is reported on libsolid which is the kdelibs4 version of the solid library.  It is now in maintenance mode.  If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid.

Comment 5 Andrew Crouthamel 2018-09-04 15:47:17 UTC

Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!