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

Occasional crash with SJTC #380

Closed
Schnilz opened this issue May 18, 2022 · 9 comments
Closed

Occasional crash with SJTC #380

Schnilz opened this issue May 18, 2022 · 9 comments
Assignees
Labels
fix pending A fix for this issue is pending in an existing PR

Comments

@Schnilz
Copy link

Schnilz commented May 18, 2022

Hi,
first of all thanks for writing this, it is awesome :)
The driver works realy well and setting it up was pretty straight forward because of the nice documentation, but i think i encountered a bug. Most of the time this issue doesn't occur but sometimes the SJTC crashes with following log messages:

[ur_ros2_control_node-1] [INFO] [1652881749.579905572] [scaled_joint_trajectory_controller]: Received new action goal
[ur_ros2_control_node-1] [INFO] [1652881749.580010468] [scaled_joint_trajectory_controller]: Accepted new action goal
[ur_ros2_control_node-1] terminate called after throwing an instance of 'std::runtime_error'
[ur_ros2_control_node-1]   what():  Executing action server but nothing is ready
[ERROR] [ur_ros2_control_node-1]: process has died [pid 57695, exit code -6, cmd ...

the error comes from rclcpp_action/src/server.cpp line 306 but im not realy sure what it actualy means :/
Like i said, reproducing it is not so easy as it works most of the time. I have a feeling it happens more often when the trajectory is short, but this could be wrong....

@fmauch
Copy link
Contributor

fmauch commented Jun 2, 2022

Thanks for posting this. This is definitively something to look into. Could you tell us a little about your setup for us to reproduce this?

  • ROS version
  • This repo version (commit hash ideally)

@fmauch fmauch added the bug Something isn't working label Jun 2, 2022
@Schnilz
Copy link
Author

Schnilz commented Jun 2, 2022

The newest commit on the glactic banch (so ae85525) with ros galactic. It is maybe caused by me not using a realtime kernel on my dual-core thinkpad which run the driver. I think that because if you put a delay (like printing to cout 10000 times) at the end of the JTC feedback callback setup function the error basicly never happens anymore (hit it once in 2h of running, compared to every ~2min before).

@fmauch fmauch self-assigned this Jun 13, 2022
@fmauch
Copy link
Contributor

fmauch commented Jun 13, 2022

This issue is not forgotten, but will need some more time to reproduce.

@RoyCLR
Copy link

RoyCLR commented Aug 23, 2022

I seems to hit the same issue, but with joint_trajectory_controller:

[ros2_control_node-1] [1661228175.046757625INFO] [joint_trajectory_controller::goal_callback]: Received new action goal
[ros2_control_node-1] [1661228175.046794670INFO] [joint_trajectory_controller::goal_callback]: Accepted new action goal
[ros2_control_node-1] terminate called after throwing an instance of 'std::runtime_error'
[ros2_control_node-1]   what():  Executing action server but nothing is ready
[ERROR] [ros2_control_node-1]: process has died [pid 1708770, exit code -6, cmd

Setup:

@fmauch
Copy link
Contributor

fmauch commented Nov 7, 2023

Coming back to this: ros2/rclcpp#2250

I've had this on my local long-term test and the linked PR fixes that for me.

@fmauch fmauch added fix pending A fix for this issue is pending in an existing PR and removed bug Something isn't working labels Nov 7, 2023
@tommy-erko
Copy link

Detailed explanation of the issue is here: ros2/rclcpp#2242

@firesurfer
Copy link
Contributor

firesurfer commented Apr 25, 2024

@fmauch Did you figure out if that fix is also backported to iron or humble ? Apparently it is finally merged into rolling but I couldn't figure out if there are plans to backport it

@fmauch
Copy link
Contributor

fmauch commented Apr 25, 2024

ros2/rclcpp#2242 (comment) not necessarily :-/

@urfeex
Copy link
Member

urfeex commented Jan 15, 2025

Seems like this got merged to humble by now.

@urfeex urfeex closed this as completed Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix pending A fix for this issue is pending in an existing PR
Projects
None yet
Development

No branches or pull requests

6 participants