Need a way to deallocate libusb delegates "leaked" after Python process is killed #36
Labels
Hardware:Accelerator Module
Coral Accelerator Module issues
stat:community support
Staus - Community Support
subtype:windows
Windos Build/installation issues
type:others
Issues not falling in bug, perfromance, support, build and install or feature
From experience on the Windows10 machine I work on, any USB socket becomes unusable for Coral USB stick if the Python/TFLite process that ran it has been killed - the OS resources stay occupied and cannot be allocated again for a given USB socket.
The only workaround I found so far is once the USB socket cannot accept Coral anymore (getting an error from edgetpu.dll), is moving Coral to another USB socket which hasn't become unusable yet, or restarting the machine, which is many times very unwanted.
Those unordinary process kills can happen while debugging, finally forcing to restart the computer when all USB sockets are allocated forever... It will be great if a script is supplied to deallocate all "leaked" allocated delegates using libusb.
The text was updated successfully, but these errors were encountered: