Hi, the wifi discover port has nothing to do with the VCP port the IDE uses to communicate to the camera. For the wifi discovery all I try to do is to bind to a particular UDP port and I display that message if the bind fails.
As for the VCP port issue. It’s true that it’s possible to have an unkillable process in windows. This happens because a thread calls a kernel level method and then that kernel method never returns making the thread get stuck in execution and unable to respond to kill signals from the OS. However, there’s no code I can write to fix this as I would have to edit the kernel driver where the issue is.
A reboot must solve this issue however. The IDE had to start the thread for it to come back. So, I can only assume you mean that you see the issue happening when you start the IDE again and you get a stuck thread.
If this is happening to you repeatedly it means your PC/USB cable may be problematic generating a condition where the kernel driver crashes and gets stuck. As the driver is closed source I can’t really say what is wrong. However, I have tried to debug this issue before and I literally found that I would make a library call with my code and that call just flat out never returns even if I removed the camera from the system.
Can you describe the exact steps in detail you do to cause this issue? Also, have you tried using a different USB cable. I definitely found the kernel driver more likely to crash if the USB cable was very long.