You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 31, 2025. It is now read-only.
The number of sockets keeps steadily climbing until the open file limit is hit. rosmaster then becomes unresponsive (e.g. rostopic list or rosnode list both just hang) and starts consuming 100% CPU.
Background:
While starting rosout in a loop isn't the most sensible thing, it's just the minimal test case to reproduce this. Trying "rosnode list" or "rostopic list" doesn't leak sockets in the same way.
I've had a few instances of this happening and it probably hasn't been rosout (but due to other pressures I haven't had the time to figure out the flaky component)