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

multithreaded executor blocked when there are 8 running nodes #2340

Closed
sgf201 opened this issue Oct 26, 2023 · 6 comments
Closed

multithreaded executor blocked when there are 8 running nodes #2340

sgf201 opened this issue Oct 26, 2023 · 6 comments
Labels
more-information-needed Further information is required

Comments

@sgf201
Copy link

sgf201 commented Oct 26, 2023

Bug report

Required Info:

  • Operating System:
    Ubuntu20
  • Installation type:
    binaries
  • Version or commit hash:
    ros2humble
  • DDS implementation:
    Fast-RTPS
  • Client library (if applicable):
    rclcpp

Steps to reproduce issue

launch 8 nodes for pull h264 stream and decode
launch 4 perception_node in multithread executor

Expected behavior

multithread executor works well
image

Actual behavior

multithreaded executor blocked
image

Additional information

img_v2_eececbea-aed2-4b1d-bcef-bf8f011671dg


@Zard-C
Copy link
Contributor

Zard-C commented Oct 26, 2023

From the log, I found process has died, exit code -11, could you check the progress status ? I don't think it's blocked.

@fujitatomoya
Copy link
Collaborator

it looks like it received segmentation fault. but we need more information, could you provide how to reproduce this issue? e.g) distribution, rmw implementation, package version.

@fujitatomoya fujitatomoya added the more-information-needed Further information is required label Oct 26, 2023
@sgf201
Copy link
Author

sgf201 commented Oct 26, 2023

From the log, I found process has died, exit code -11, could you check the progress status ? I don't think it's blocked.
It is blocked for a long while ,then crashed

@Zard-C
Copy link
Contributor

Zard-C commented Oct 26, 2023

From the log, I found process has died, exit code -11, could you check the progress status ? I don't think it's blocked.
It is blocked for a long while ,then crashed

could you add this detail to Bug Report?

as you described:

  1. The Executor was spinning but no callback was called, which was not expected to.
  2. The Executor spin for a while (how long ?) then the the progress was recieved signal 11 (which is SIGSEGV) .

Out of my head, I have no explanation, why it was blocked, could you provide more information about how to reproduce this issue?

Besides, you can run the program with gdb, and check where it crashed, maybe it's an important clue.

@Zard-C
Copy link
Contributor

Zard-C commented Oct 27, 2023

@sgf201 any update 😄 ?

@sgf201
Copy link
Author

sgf201 commented Dec 11, 2023

thread safe problem ,4 nodes crashed on the save object. thanks

@sgf201 sgf201 closed this as completed Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more-information-needed Further information is required
Projects
None yet
Development

No branches or pull requests

3 participants