-
Notifications
You must be signed in to change notification settings - Fork 65
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
OccupancyGridStamped Rviz plugin crashed #25
Comments
I don't think there's a working visualization for OcTreeStamped, and probably there's not a proper check in place to catch that error.
|
I see. I assumed that there was because I can choose the plugin OccupancyGridStamped in RViz and also the code is templated to OcTreeStamped. So is there are an obvious reason that this wouldn't work with OcTreeStamped? The data structures aren't fundamentally different (actually not at all?), right? Via debugging, I've located that the segmentation fault occurs in this line: Any quick ideas? Otherwise I'll try to find a fix myself. Thanks anyway for the quick reply! |
I found the problem. It's that octomap_msgs::msgToMap, or more specifically binaryMsgToMap does not handle OcTreeStamped but only OcTree and ColorOcTree and then returns null. Probably the same issue as here. It works when OcTreeStamped is added to that function. |
Does Anyone fix this bug? |
Apparently it should be fixed, cf. OctoMap/octomap_msgs@2b390b6 Did you encounter this issue? And if so, what versions of octomap_rviz_plugins are you running on which platform? |
Hi, I'm publishing an OcTreeStamped and want to visualize it with RVIZ. However, when I set the topic /octomap for the plugin in RVIZ, RVIZ crashes completely. I've tried it on three different computers with Ubuntu 16.04 and ROS Kinetic. One computer gives "Segmentation fault (core dumped)". The other two only give "process has died [pid 4342, exit code -11...".
Is this a known issue?
The text was updated successfully, but these errors were encountered: