Closed peci1 closed 6 months ago
This issue has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-noetic-sync-2024-05-09/37602/2
Fixed via e0ec5f6b5d4b06042c51501c20fb6f6a1c5d4f0d
Oh, great, thanks a lot for the quick action, @rhaschke ! I really didn't know what the culprit could be... I verified your fix works.
Thanks a lot, Martin, for your excellent bug report. That helped a lot to pinpoint the issue quickly.
I am still getting this issue (or at least very similar) on latest noetic-devel
(2db2c5394a4f1fcf5fecfb8d0952d4f913c04aee).
Renaming a rviz/RobotModel
display and relaunching causes RViz to crash. Reverting to version 1.14.20 makes it work again with the issue being introduced in 1.14.21. I cannot reproduce with the example provided by @peci1 so this might be a different issue. I will try to create a minimally reproducible example and post here or create a new issue but my guess is that I've found an edge case that's not solved by @rhaschke's fix.
@Achllle: I cannot reproduce your issue. As you complain about renaming the display (from RobotModel
) and not about renaming the topic, I guess that's a different issue. Please open a new issue report and provide a detailed description how to reproduce the error. If you have an rviz config reproducing it, please upload that file.
Your environment
echo "$LANG $LC_NUMERIC"
: cs_CZ.UTF-8 Before reporting a rendering issue, try running RViz withLANG=C rviz
! - no effectDescription
Commit df72fce669683e01a67156bec3f847f6449b30a7 from #1808 broke loading rviz with a config that contains RobotModel display configured for non-default parameter name (e.g.
robot_description2
). This only happens whenrobot_description
also contains something, which is very weird, because I'd say that if the config only contains RobotModel withrobot_description2
, it should not touchrobot_description
at all. But it does and it leads to segfault.Repro
a.urdf:
c.urdf:
b.rviz:
bug.launch:
When you launch
roslaunch ./bug.launch
, rviz 1.14.22 segfaults. When you launchroslaunch ./bug.launch bug:=false
, it launches correctly (that corresponds to not settingrobot_description
). Be sure to let roslaunch create its own rosmaster when doing these tests.GDB backtrace
Analysis
Git blame pointed at commit df72fce669683e01a67156bec3f847f6449b30a7. When I revert it, the bug does not manifest.
If I start an empty RViz and add the RobotModel display to it, no segfaults happen. But when I save it and rerun RViz with this config, and
robot_description
is set, the segfault happens.