-
Notifications
You must be signed in to change notification settings - Fork 466
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
TF display segfault (openni_tracker related) #808
Comments
Thanks for the report, and for taking the time to describe how to reproduce it. Looks like the problem manifest at either: or Though neither jump out at me as implicitly wrong. Unfortunately, without a traceback on rviz built with debug, this isn't going to be enough information. My rviz issue queue is pretty backed up, so I probably won't have time to reproduce this problem locally in the near term. |
Hello, I am also seeing a crash of rviz (segmentation fault) when running a minimal rviz config with only tf enabled. It seems to only be happening when there are appearing/disappearing transforms. A bag file which crashes rviz at the end of the bag: rviz_tf_crash_ar_markers.bag In this bag file our robot is driving in our office and the ar_track_alvar node is running. On the wall there are a number of markers which you can see appear and disappear a number of times. When driving around with ar_track_alvar disabled or when the markers are not in the field of view of the kinect rviz seems not crash. I'm also running hydro on Ubuntu 12.04, everything up to date as of today. Rviz GDB backtrace:
|
Thanks for the added comment @OkkeHendriks, unfortunately your backtrace is also of a non-debug version of rviz, and so there are no line numbers to give us a hint, but it is most likely a cross thread race condition in this code path. |
…et/create Do not needlessly delete tree_property_ elements, update them instead. Most likely fixes ros-visualization#808 too.
…et/update Do not needlessly delete tree_property_ elements, update them instead. Most likely fixes ros-visualization#808 too.
I found that #926 solved this issue on my machine using the skeleton bag example in the OP. Please comment if anyone still has a problem with this. Unfortunately it will only go out into Indigo and Jade since Hydro is eol and I cannot make new releases of it. |
Hi wjwwood, I'm getting into the same segfault on rviz whenever I add a new tf. This is the debug output: I'm sorry, I don't know how to extract info about the exact line of the error, and I saw that the updateFrame function is quite huge xD |
I'm attempting to play a bag file captured from
openni_tracker
(skeleton tracking using the kinect), with an additional (custom) frame meant to provide a global reference. The custom frame is produced using a static transform publisher started in the launch file. During playback, RViz crashes if the TF plugin is loaded. If I don't load the TF plugin, RViz is fine; other nodes I'm running that do transforms betweenglobal
and other frames also seem happy.The crash can be reproduced by launching the following (note that I left
gdb
in there):then playing a bag file that recorded the
/tf
topic produced byopenni_tracker
:I'm not sure I got the static transform correct, which is why I was attempting to view the TF frames. Since I can't post the bag file and the
.rviz
file is a bit unwieldy, all three files (gdb_rviz.launch
,skeleton.bag.tar.gz
, andtf_debug.rviz
) are available at: https://personal.traclabs.com/~jkramer3/.The crash happens about 8 seconds in, with the following gdb backtrace:
I'm running hydro on Ubuntu 12.04, everything up to date as of today.
The text was updated successfully, but these errors were encountered: