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

Intra Process Communication demo stalls on Q or Esc key press #297

Open
gonzodepedro opened this issue Dec 12, 2018 · 9 comments
Open

Intra Process Communication demo stalls on Q or Esc key press #297

gonzodepedro opened this issue Dec 12, 2018 · 9 comments
Labels
bug Something isn't working

Comments

@gonzodepedro
Copy link
Contributor

gonzodepedro commented Dec 12, 2018

Bug report

Required Info:

  • Operating System:
    • Ubuntu 18.04
  • Installation type:
    • binaries (.deb)
  • Version or commit hash:
    • Crystal
  • DDS implementation:
    • RTI Connext
  • Client library (if applicable):
    • rclcpp

Steps to reproduce issue

Run intra process demo:
ros2 run intra_process_demo image_pipeline_all_in_one
Press Esc or Q key

Expected behavior

Application should exit in a reasonable time

Actual behavior

Application stalls for longer than 30 seconds and exists

Additional information

No error on console. Application stops responding to commands. Application exits without errors with SIGINT. Application exists normally but takes a long time.

@wjwwood
Copy link
Member

wjwwood commented Dec 12, 2018

@hidmic could this be related to our changes? Did we try a self exiting application?

@wjwwood
Copy link
Member

wjwwood commented Dec 12, 2018

Oh this is with debs, maybe not then. Also this is rclcpp not rclpy as the issue template says. Unless it is hanging in ros2 run.

@hidmic
Copy link
Contributor

hidmic commented Dec 12, 2018

This might be a duplicate of #290. If nothing is published on the topic, the viewer becomes unresponsive to user input. @gonzodepedro could you validate this?

@gonzodepedro
Copy link
Contributor Author

gonzodepedro commented Dec 12, 2018

Been testing a little further. It finally exists. But it takes a lot (around 30 seconds) to exit.

@wjwwood
Copy link
Member

wjwwood commented Dec 12, 2018

Connext is known to take a long time to shutdown, but not that long (30 seconds). Compare with ctrl-c on something like ros2 run demo_nodes_cpp talker.

@gonzodepedro
Copy link
Contributor Author

This might be a duplicate of #290. If nothing is published on the topic, the viewer becomes unresponsive to user input. @gonzodepedro could you validate this?

I don't think it's a duplicate of 290

@gonzodepedro
Copy link
Contributor Author

Connext is known to take a long time to shutdown, but not that long (30 seconds). Compare with ctrl-c on something like ros2 run demo_nodes_cpp talker.

Takes longer than SIGINT on ros2 run demo_nodes_cpp talker.

@wjwwood
Copy link
Member

wjwwood commented Dec 12, 2018

Running with the command line argument __log_level:=debug might shed some light.

@jacobperron
Copy link
Member

Also happens on OSX (High Sierra) with the latest binaries.

@jacobperron jacobperron reopened this Dec 14, 2018
@clalancette clalancette added the bug Something isn't working label Dec 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants