-
Notifications
You must be signed in to change notification settings - Fork 219
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
Rviz2 crashes with footprint drawing #574
Comments
@daisukes I'm not able to reproduce the error. I've tried to follow the provided steps with Foxy Debian packages installed, but it doesn't look the the simulation is starting properly (the world looks empty with a laser scan visible). I see the following logs repeated in the terminal:
Is there a simpler example you can provide to reproduce the issue? |
@jacobperron Thank you for taking the time! In order to enable simulation, you need to set Gazebo env before launching the simulation.
|
@daisukes Thanks, I can see the world and robot model in Gazebo now, but I'm still getting the same TF-related logs about invalid "odom" frame. I don't see any footprint in RViz. |
There was a recent fix to the tf2 message filter (ros2/geometry2#279). @daisukes Since the stack traces you provided indicate that the tf2 message filter is involved, could you try the latest Foxy release and see if you can still reproduce this? |
Thanks, I will check with the latest Foxy release.
Foxy has an issue with Fast-RTPS, which is recently fixed. Using cyclonedds may help the issue.
|
With the latest Foxy release (ros2/ros2@4109e26), it looks the issue has been gone. So, I close this issue, and again thank you very much! |
OS: Ubuntu focal
ROS2: foxy binary / foxy release src build (ros2/ros2@fc010c9#diff-215a2eb6c7ad8b20796a9fceb48f8cc7)
Issue
I have been working with Navigation2 and experiencing Rviz2 crash sometimes when the controller is ready and drawing (binary), sometimes the display option is changed (both src, binary).
It looks like footprint drawing causes this crash.
A workaround is to uncheck "Controller/Polygon", or use an src build and do not change the display option.
This could not reproduce 100% the crash but, got crash often.
Backtrace with the binary build, crashed instantly (click to open)
Backtrace with the src build (crashed after changing display option)
The text was updated successfully, but these errors were encountered: