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

Camera display type crashes rviz (Melodic) when deselected or deleted #1372

Closed
ashnap123 opened this issue Apr 29, 2019 · 4 comments · Fixed by #1404
Closed

Camera display type crashes rviz (Melodic) when deselected or deleted #1372

ashnap123 opened this issue Apr 29, 2019 · 4 comments · Fixed by #1404

Comments

@ashnap123
Copy link

ashnap123 commented Apr 29, 2019

Camera display type crashes rviz when it it deselected or deleted. Recreated with multiple cameras on multiple machines.

To recreate

  • Add any camera with a valid calibration
    rviz_add camera

  • Camera display image should be displayed with overlay
    rviz_camer_active

  • Either delete or de-select Camera display to cause crash.
    rviz_crash

Your environment

  • OS Version: Ubuntu 18.04

  • ROS Distro: Melodic

  • RViz, Qt, OGRE, OpenGl version as printed by rviz:
    rviz version 1.13.3
    compiled against Qt version 5.9.5
    compiled against OGRE version 1.9.0 (Ghadamon)
    Stereo is NOT SUPPORTED
    OpenGl version: 4.6 (GLSL 4.6).

  • Console output

Gtk-Message: 12:27:56.341: GtkDialog mapped without a transient parent. This is discouraged.
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument
[1]    25031 abort (core dumped)  rviz
  • Install type
    Aptitude
@mcsheehan
Copy link

I'd like to bump this as a fairly major issue. The program crashes on moving camera windows around.

@rhaschke
Copy link
Contributor

Upstream issue: ros/geometry2#402.

rhaschke added a commit to rhaschke/rviz that referenced this issue Aug 26, 2019
rhaschke added a commit to rhaschke/rviz that referenced this issue Aug 30, 2019
... also when clearing tf_filter_ in reset()
Otherwise received messages might be reported, which were outdated.
rhaschke added a commit to rhaschke/rviz that referenced this issue Apr 16, 2020
This reverts commit 5ab445b.
This reverts commit 42eed97.
This reverts commit 371b23a partially.

As ros/geometry2#402 is released since tf2 >= 0.6.6,
we can revert these hot fixes.
rhaschke added a commit to rhaschke/rviz that referenced this issue May 3, 2020
The release 0.6.6 of tf2 was reverted. The bug is still there.
@tsukione
Copy link

tsukione commented Sep 24, 2021

25d2c81 made this issue reappear @rhaschke

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument
Signal: SIGABRT (Aborted)

@rhaschke
Copy link
Contributor

Sorry. I was fooled by the fact that there was a release 0.6.7 of TF2. However, it never made it into the distro: ros/geometry2#520. Looks like, we still need the workaround for Melodic.

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

Successfully merging a pull request may close this issue.

4 participants