-
Notifications
You must be signed in to change notification settings - Fork 376
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
Using with Ros2: Ros2webbridge crashes after a period of time #376
Comments
Hi @slogan-oxts , |
Yes I did try the resolution in that ticket but it seemed to make no difference. I've managed to get a test using only ros2webbridge working and it seems to fail with the same issue so it looks like the issue is probably in there. I'll close this one for now and make a ticket on that repository. |
Thanks @slogan-oxts , please feel free to reopen if you see that the problem is related to ROS#. |
The solution to this issue was to use a different version of node.js. The latest erbium release (12.20.1 at the time of writing). After installing this is seems to be working perfectly both inside and outside of ROS#. More information in the ros2webbridge ticket: |
I have a question!
Here is my question:
I'm trying to use Ros# with Ros2 using Ros2webbridge.
I get the messages in unity but after a length of time (< 1 minute) after subscribing, Ros2webbridge crashes with the error:
or sometimes:
My unity code is looks like this:
The topics are being published at 100Hz by a simple python script using rclpy, though I was originally trying to replay a bag file sending topics at a similar rate with the same results.
I've tried downgrading Node.js to version 12.9.0. It lasts much longer using this version (5-10 minutes) but eventually closes with no error.
I'm very new to Ros/Ros2 so I'm not sure how to test the Ros2webbridge independent of Ros# though the issue only ever happens after the application has subscribed to the topics.
The more topics I subscribe to the faster it seems to crash as well.
The text was updated successfully, but these errors were encountered: