With reference to the  issue 683855  , ccing related dev  for further inputs on this issue.

@arti3d.artem-- It would be helpful for us if you could provide a sample app to test the scenario and also please provide us the chrome version details.

Thanks!

You can use official sample app: https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/hid

 And create global receiver that works forever:

setInterval(function(){
    chrome.hid.receive(function(reportId, data) {
        console.log(data);
    });
}, 10) 

And then send few commands to your HID device. After 1-2 min your CPU will raise to 100% and chrome disconnect event will fired.

The chrome.hid.receive function is not cancelable so the behavior of seeing "This is old function" as in the Stackoverflow post is expected.

However, the 100% CPU usage is definitely not expected. You say you eventually get a disconnect event. Is the device actually disconnected?

Oh sorry, disconnect event caused by device. Yes device is connected, and return data when i send commands. I put console.log(data) into receive function and i see the following log after my command:

First i received my data, and then i started get undefined data until my cpu not get 100%.

Deleted: Preview5 (1).gif 6.2 MB

	Preview5 (1).gif 6.2 MB View Download

Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919 

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot