-
Notifications
You must be signed in to change notification settings - Fork 72
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
crash in foxglove ros1 due to pointer #267
Labels
bug
Something isn't working
Comments
Internal tracking ticket: FG-5366 |
@weidezhang I have submitted a potential fix in #268. Could you confirm if that fixes the crash? |
@achim-k cool. seems the issue is fixed. i have verified locally. thx for the quick response. |
achim-k
added a commit
that referenced
this issue
Oct 23, 2023
### Public-Facing Changes Fix callback accessing invalid reference to promise ### Description For ROS1, the service request and response types can only be retrieved by opening a connection to the service server. For this, we use `ros::ServiceManager::instance()->createServiceServerLink` which under the hood keeps a copy of the returned pointer, effectively keeping the connection alive. This patch makes sure that we drop the connection when we either have received the header or when the timeout has been exceeded. This avoids that the header-received callback is being called with an invalid reference to the promise. Fixes #267 Resolves FG-5366
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
By restarting some of our ros nodes , we found foxglove_bridge_ros1 crash randomly.
Steps To Reproduce
By bringing up and bringing down our ros nodes (with / without rviz), we found the following core dump :
Expected Behavior
should not crash
The text was updated successfully, but these errors were encountered: