Hi, I have just migrated our client from the old Jabra .NET SDK to the new V2 SDK. I'm using build v1.3.0.0 from July.

One internal beta user is experiencing high CPU load (25%) when the client software is running on his Lenovo notebook. Using process explorer I could narrow it down to the thread libjabra.dll!Jabra_WriteHIDCommand. The CPU load stops when I unplug the device (Jabra Pro 930) and it is again on 25%. The same CPU load shows up when I connect an Evolve 80.

I have downgraded the client installation to the previous version, using Jabra .NET SDK v3.1.13407 and the issue is gone.

I cannot reproduce the issue on my machine (Dell notebook).

hi, could you detail the windows revision you are seeing this issue on? many thanks.

Machine with high CPU load:
Windows 10 Home
Version 1803
OS build 17134.345


Other machine working correctly:
Windows 10 Pro
Version 1803
OS build 17134.345


In both cases the application is running as 64bit process.

hi, we have released an new SDK to address this issue.

https://developer.jabra.com/site/global/sdks/windows/index.gsp

v1.4

thanks.

Thanks, I will let the beta users try the new build.

It appears, that the lock / unlock scheme has been removed from the SDK. I expect that this is no longer required?


Wolfgang

The bugfix works for both beta users. I expect that the issue is solved.

Wolfgang

Unfortunate this issue seems NOT be fixed with the latest SDK build (1.8.3.10) running on Win 10 Pro 1809 and a Evolve 75 attached.
The CPU fan of my Dell notebook indicates full load on one CPU core (-> 25%) just after (auto)starting the Jabra Direct suite. I#ll took a look to the call stack of the thread in questions with ProcMon and it showed the same looping on the libjabra.dll!Jabra_WriteHIDCommand mentioned in the initial post!

I tried restart 2-3 times and the issue reproduces stable all the times ;-/

best regards
Ralf

Hi Ralf,

version 1.8.3.10 does contain a fix for the 100% CPU consumption issue.
In fact, we have been unable to reproduce the behaviour on applications linked with the new core libraries from 1.8 and onwards.

The current production release of Jabra Direct is using a slightly older version of the core libraries (1.7.9.x), and this is most likely why we see the behaviour with Direct. The behaviour is also likely to disappear when Direct is upgraded later in the spring to use version 1.8.x or later.

Hi Sten,

thank you for your reply! This makes some sense to me

I looked up the audio SDK version in use and found 1.7.9.1. So I'll await the new Jabra Direct version and report back then...


Best regards
Ralf Bonenkamp