You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 11, 2026. It is now read-only.
Describe the bug
When the driver closes a file HANDLE, the UwbConnector continues looping forever trying to issue the DeviceIoControl call.
Steps To Reproduce
Start a session with nocli, then forcibly unload the driver.
Expected behavior UwbConnector::HandleNotifications should properly handle the return value E_INVALID_HANDLE. At minimum, it must discard the current HANDLE it is using.
Actual behavior UwbConnector::HandleNotifications loops forever, repeatedly calling DeviceIoControl with an invalid HANDLE.
Describe the bug
When the driver closes a file
HANDLE, theUwbConnectorcontinues looping forever trying to issue theDeviceIoControlcall.Steps To Reproduce
Start a session with
nocli, then forcibly unload the driver.Expected behavior
UwbConnector::HandleNotificationsshould properly handle the return valueE_INVALID_HANDLE. At minimum, it must discard the currentHANDLEit is using.Actual behavior
UwbConnector::HandleNotificationsloops forever, repeatedly callingDeviceIoControlwith an invalidHANDLE.