-
Notifications
You must be signed in to change notification settings - Fork 431
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
Investigate possible segfaults in expanded executors unit tests #1230
Comments
Looks like I hit a related segfault in this PR job: http://build.ros2.org/job/Rpr__rclcpp__ubuntu_focal_amd64/210 |
Possibly related: #447 I suspect these segfaults, which occur during destruction, would occur for a test that just initializes and destroys many nodes. |
@jacobperron Yup, that looks like one of these failures. Are you seeing it show up more often than the 5% I found on local testing? |
I just noticed it once during the Rpr job in #1257 and in searching if it was a known issue came across this ticket. Just reporting it in case it's any help. |
I think these have been cleaned up finally, especially with #1404 |
The executors unit test is being expanded in #1222, and running it consecutively hundreds of times shows that about 5-6% it will exit with a segfault across several different executors in several different functions. Unfortunately, simple tracing with gdb is not yielding much info.
Copying the results of the investigation here:
Here were all the instances of segfaults with duplicates.
Running valgrind on this test executable results in:
And a read error
Unrelated to the segfaults, these stderr messages are also outputted.
The text was updated successfully, but these errors were encountered: