-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closing Port COM while receiving data often creates a Deadlock in application #20
Comments
yes this might be a problem in the core libraries, so we can ignore it. |
But can we try to find a working workaround and then put it into the library ? |
Yes if the work-around can be done in serial-port-lib. |
but better do this in a different pull-request |
Actually I didn't found a stable workaround. If I do, I'll post a pull request. |
Fixed by #26 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I found an issue when closing Port COM while sending data. It creates a Deadlock in the application.
This is the stack trace below :
The execution pointer is blocked in method
when executing
I think that this deadlock occurs in native Framework
SerialPort
.I've no idea how to solve this, beside waiting the end of transmission...
See this thread : https://social.msdn.microsoft.com/Forums/en-US/ce8ce1a3-64ed-4f26-b9ad-e2ff1d3be0a5/serial-port-hangs-whilst-closing?forum=Vsexpressvcs
Regards
The text was updated successfully, but these errors were encountered: