-
Notifications
You must be signed in to change notification settings - Fork 126
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
Segmentation fault in libsensor_msgs__rosidl_typesupport_fastrtps_cpp.so #490
Comments
Since it segfaults in |
No. I tried it again. I have 24GB memory and the system is using only 7GB in total when I got the error again. |
@dirk-thomas Thanks to the hint, I might fix the issue by increasing the stack size. It has been running over 20 minutes so far.
|
Since 8192 is the default on Ubuntu and with that configuration it works for many developers, users as well as our CI infrastructure I don't think it should be necessary. A debug build and using |
I tried a debug build. While building, my system used all disks and my docker environment was broken. If I get the same error again, I will be back here, but this issue can be closed I think. |
Bug report
It looks like something wrong in deserializing LaserScan message once per thousands.
It happens in 30 secs to several mins from launch randomly and /scan message is published in 10hz.
I have been working on my ROS1 system with ROS2 navigation.
ROS1+Gazebo simulate Velodyne lidar and convert it to LaserSacn and transfer it to ROS2 via a bridge.
I'm not sure that this is a bug here or my configuration with the bridge. Could you help me to fix this?
Required Info:
Steps to reproduce issue
It is difficult because my project is not public yet, but here is the backtrace of the process.
This could happen with the process which subscribing to the /scan message.
The text was updated successfully, but these errors were encountered: