100% cpu usage after disconnect MCE remote (1 Viewer)

[djonline]

You don't understand me.
IRSS shouldn't hang-up or eat CPU after disconnecting USB receiver. IRSS must simple sleep and wait for moment, when USB receiver will be connected again.

 

[djonline]

Still the same with latest IR Server 1.4.2.4189.zip
100% cpu after disconnect USB MCE.
Changelog from 1.4.2.3650 "Added hardwareMonitor which listens to usb device connects or disconnects" not help at all.

 

[chemelli]

unfortunately this is a by-design issue with that specific hardware. The polling to the receiver is performed so quickly and continuously from the driver that the CPU spikes.

I bet the MS dev would have though "why should one remove the receiver?".

Simone

 

[tourettes]

I bet the MS dev would have though "why should one remove the receiver?"

And here is a developer who don't understand who has hired such developer to MS (especially if the driver is polling constantly - it was done on DOS days, but not in the current time. Unless the HW developers where having few screws that would need some tighting up )

 

[djonline]

After restarting ir service cpu is 0% with disconnected USB, but after connecting back ir not work, so i again restart usb.
Not usefull at all.

 

[chemelli]

I bet the MS dev would have though "why should one remove the receiver?"

And here is a developer who don't understand who has hired such developer to MS (especially if the driver is polling constantly - it was done on DOS days, but not in the current time. Unless the HW developers where having few screws that would need some tighting up )

Simone

 

[djonline]

But what about 'hardwareMonitor' ?
What is it and why it not working ?

 

[chemelli]

It's working for some drivers/hardware, it all depend on how the interface is implemented by the vendor.

Simone