-
Notifications
You must be signed in to change notification settings - Fork 400
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
lcm-dotnet Close() not working #17
Comments
Thanks for the contribution. Could you submit that as a pull request? |
closed by #18 |
miquelmassot
pushed a commit
to miquelmassot/lcm
that referenced
this issue
Sep 9, 2024
Closes lcm-proj#17 This uses another naive algorithm but, again, I really doubt that matters in this particular case.
miquelmassot
pushed a commit
to miquelmassot/lcm
that referenced
this issue
Sep 9, 2024
Fix hashes and `use` errors Closes lcm-proj#17 and lcm-proj#18
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I encountered this issue that when invoke LCM.Close(), the function halts forever. I think similar issue was brought up in lcm-java and it was fixed in the java version. Yet in the dotnet version it still exists. Since dotnet thread doesn't have similar isInterrupted() functionality, I made following changes and it seemed work. I attached the patch here. Hope it might help :)
The text was updated successfully, but these errors were encountered: