-
Notifications
You must be signed in to change notification settings - Fork 17
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
Websocket segfault when quickly opening and closing connections #60
Comments
I'm also seeing a similar segfault when attempting to open a connection at all, without even quickly cycling the connection:
This is simply when using the visualization app hosted from the gazebosim site: Core dump with crash file: _usr_lib_x86_64-linux-gnu_gz_launch6_gz-launch.1000.zip System info:
|
Found something interesting regarding this bug. I am able to reproduce it using docker with this Dockerfile: ARG ROS_VERSION=humble
FROM ros:$ROS_VERSION
RUN apt-get update && apt-get install -y --no-install-recommends wget curl
ARG GAZEBO_VERSION=garden
RUN wget https://packages.osrfoundation.org/gazebo.gpg -O /usr/share/keyrings/pkgs-osrf-archive-keyring.gpg && \
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/pkgs-osrf-archive-keyring.gpg] http://packages.osrfoundation.org/gazebo/ubuntu-stable $(lsb_release -cs) main" | tee /etc/apt/sources.list.d/gazebo-stable.list > /dev/null && \
apt-get update && \
apt-get install -y --no-install-recommends gz-$GAZEBO_VERSION ros-$ROS_DISTRO-ros-gz$GAZEBO_VERSION
RUN curl -O https://raw.githubusercontent.com/gazebosim/gz-launch/main/examples/websocket.gzlaunch
CMD bash -c "gz sim -s -v 4 shapes.sdf & gz launch -v 4 websocket.gzlaunch" And running this command: However, if I run with I'm curious if @ruffsl was also using Docker / network host when he encountered the bug. This is not a root cause of course, but could point someone more knowledgeable in the right direction. |
@usedhondacivic , I think I probably was using the
Perhaps this as something to do with unusual differences in process namespace isolation in containers vs matching host names with host network interfaces throwing off ZeroMQ, similarly to what I've experienced with DDS and shared memory transport? |
The Websocket server segfaults if a websocket connection is opened and closed in quick succession.
Steps to reproduce
Stack trace
The text was updated successfully, but these errors were encountered: