Skip to content
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

RVIZ segfault and assertion when visualising pointcloud2 #717

Closed
SentinalBais opened this issue Feb 6, 2014 · 2 comments
Closed

RVIZ segfault and assertion when visualising pointcloud2 #717

SentinalBais opened this issue Feb 6, 2014 · 2 comments

Comments

@SentinalBais
Copy link

Hi I am using the following RVIZ

Ubantu 12.04 64 bit
Intel i5 , integrated graphics (intel hd graphics )

rviz version 1.9.34
[ INFO] [1391693318.932947785]: compiled against OGRE version 1.7.4 (Cthugha)
[ INFO] [1391693319.263403304]: OpenGl version: 3 (GLSL 1.3).

I got an update yesterday, which seemed to break the visualisation of pointclouds in rviz (segfault). Before the update pointclouds were being displayed fine.

I made a ROS answers thread, there is a sample pcd file (.jpg) which causes the segfault when I try to visualise it in RVIZ. If I visualise it in small steps say 10 points, then close the publisher then visualise 20 points, no segfault occurs. However if i edit the pcd file and so i visualise 100 points all at one a segfault occurs

once I got this error rviz: ../../../../../src/glsl/ralloc.c:81: get_header: Assertion `info->canary == 0x5A1106' failed.

ROS answers thread
http://answers.ros.org/question/126766/ros-rviz-groovy-segfault-and-assertion-fail/

Also sometimes RVIZ crashes the screen flashes and all the task bars disappears. So maybe there are some driver issues with the latest update to RVIZ

@wjwwood
Copy link
Member

wjwwood commented Feb 6, 2014

May be related to #713

@wjwwood
Copy link
Member

wjwwood commented Feb 25, 2014

@SentinalBais I believe #713 addresses your issue. 1.9.35 is on its way and should fix the problem.

I am going to close this, please comment here if your problem is not resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants