-
-
Notifications
You must be signed in to change notification settings - Fork 469
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 segfaults when node that publishes marker crashes (ros-pkg ticket #4463) #356
Comments
[watts] I probably should've noted that I'm using stage as an erratic simulator. {{{ |
[jfaust] backtrace? |
[watts] I managed to reproduce this problem on my desktop, here is the backtrace: {{{ {{{ Thread 16 (Thread 21416): Thread 15 (Thread 21410): Thread 14 (Thread 21426): Thread 13 (Thread 21425): Thread 12 (Thread 21427): Thread 11 (Thread 21441): Thread 10 (Thread 21434): Thread 9 (Thread 21435): Thread 8 (Thread 21433): Thread 7 (Thread 21424): Thread 6 (Thread 21423): Thread 5 (Thread 21436): Thread 4 (Thread 21415): Thread 3 (Thread 21412): Thread 2 (Thread 21414): Thread 1 (Thread 21453): |
[jfaust] If that's where it's crashing, that looks a lot like a driver bug. What's your nvidia driver version? |
[jfaust] oh... and following your instructions it works fine with the cturtle debs on my machine. I have a version of the 195.36.31 driver |
[watts] I'm using the nVidia developer drivers on both machines, version 260.24. That could explain this. Once nVidia releases a new version of their driver, I can test it with that to see if the problem goes away. I'm glad this works on the real drivers. |
[jfaust] Definitely a driver problem. See #4461 |
…tionFinder (ros-visualization#356) To fix the following warnings (converted to errors by compile options): error: destructor called on non-final 'MockProjectionFinder' that has virtual functions but non-virtual destructor [-Werror,-Wdelete-non-virtual-dtor] error: destructor called on non-final 'MockWindowManagerInterface' that has virtual functions but non-virtual destructor [-Werror,-Wdelete-non-virtual-dtor]
I've got a simple node that publishes a marker to rviz. Whenever I kill the node with "ctrl-c", rviz segfaults and crashes. I'm sure I have a problem with my node, that I will fix, but it looks like rviz doesn't like it when a publisher hangs up on it.
My package "sticky_marker" is attached. To duplicate this failure,
rviz output below:$exepath "$ @"
{{{
$ rosrun rviz rviz
[ INFO] [1285917248.573214978]: Loading general config from [/home/wgtest/.rviz/config]
[ INFO] [1285917248.573802483]: Loading display config from [/home/wgtest/.rviz/display_config]
[ WARN] [1285917249.734839707, 1127.200000000]: Message from [/stageros] has a non-fully-qualified frame_id [base_laser_link]. Resolved locally to [/base_laser_link]. This is will likely not work in multi-robot systems. This message will only print once.
[ WARN] [1285917329.358039007, 1206.900000000]: Message from [/sticky_1285917329053921114] has a non-fully-qualified frame_id [odom]. Resolved locally to [/odom]. This is will likely not work in multi-robot systems. This message will only print once.
[ WARN] [1285917360.963096573, 1238.500000000]: Message from [/sticky_1285917329053921114] has a non-fully-qualified frame_id [odom]. Resolved locally to [/odom]. This is will likely not work in multi-robot systems. This message will only print once.
/opt/ros/cturtle/ros/bin/rosrun: line 35: 11131 Segmentation fault
}}}
Tarball of sticky_marker package and rviz configuration files are attached. Using deb build of ROS cturtle, 1.2.1, visualization 1.2.0.
trac data:
The text was updated successfully, but these errors were encountered: