{noetic} Fixing infinite loop with roslogging and python3.12 #1329
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes an issue described in [this issue](ros/ros_comm#2352 (comment)) Basically, due to python3.12, which is default in styhead, the roslogging is stuck in an infinite loop trying to get the caller stack. Hence, roscore is at 100% CPU but does not work, nor does any other node. This is a different solution as the suggested in the issue. Signed-off-by: Matthias Schoepfer <msc@fp-robotics.com>
Collaborator
|
Thanks, I will put this on the queue for merging in. |
Collaborator
|
I did a visual review. This looks good. I will add it to my merge queue. |
robwoolley
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes an issue described in
this issue
Basically, due to python3.12, which is default in styhead, the roslogging is stuck in an infinite loop trying to get the caller stack. Hence, roscore is at 100% CPU but does not work, nor does any other node.
This is a different solution as the suggested in the issue.