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
I believe usb_free_async should check return value of CloseHandle. Otherwise a situation when CloseHandle fails for some reason and not actually closes handle but usb_context_t is being freed nevertheless is entirely possible. This would lead to a resource leak which is nearly impossible to diagnose from a user application.
The text was updated successfully, but these errors were encountered:
libusb-win32 project is in a support only mode. Mailing list support is still provided, no changes to the codes and release, unless critical bug found and the fixes are feasible.
https://sourceforge.net/p/libusb-win32/patches/14/
Updated: 2012-07-06 Created: 2012-01-30 Creator: Kirill Batuzov
I believe usb_free_async should check return value of CloseHandle. Otherwise a situation when CloseHandle fails for some reason and not actually closes handle but usb_context_t is being freed nevertheless is entirely possible. This would lead to a resource leak which is nearly impossible to diagnose from a user application.
The text was updated successfully, but these errors were encountered: