Mutex assertion crash - gzserver

[TedVanderfeen]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

roslaunch gazebo_ros empty_world.launch
... logging to /home/ted/.ros/log/dca2c6e0-aa5a-11f0-8b54-cc96e5467053/roslaunch-localhost-22574.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://localhost:45039/

SUMMARY

PARAMETERS

• /gazebo/enable_ros_network: True
• /rosdistro: noetic
• /rosversion: 1.17.0
• /use_sim_time: True

NODES
/
gazebo (gazebo_ros/gzserver)
gazebo_gui (gazebo_ros/gzclient)

auto-starting new master
process[master]: started with pid [22612]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to dca2c6e0-aa5a-11f0-8b54-cc96e5467053
process[rosout-1]: started with pid [22660]
started core service [/rosout]
process[gazebo-2]: started with pid [22663]
process[gazebo_gui-3]: started with pid [22665]
[ INFO] [1760596768.321307330]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1760596768.322029474]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1760596768.436637068]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1760596768.439198434]: waitForService: Service [/gazebo_gui/set_physics_properties] has not been advertised, waiting...
Fatal glibc error: pthread_mutex_lock.c:94 (___pthread_mutex_lock): assertion failed: mutex->__data.__owner == 0
Aborted (core dumped)
[gazebo-2] process has died [pid 22663, exit code 134, cmd /home/ted/repos/project/.pixi/envs/gz-test/lib/gazebo_ros/gzserver -e ode worlds/empty.world __name:=gazebo __log:=/home/ted/.ros/log/dca2c6e0-aa5a-11f0-8b54-cc96e5467053/gazebo-2.log].
log file: /home/ted/.ros/log/dca2c6e0-aa5a-11f0-8b54-cc96e5467053/gazebo-2*.log

Installed packages

To follow

Environment info

Environment: gz-test
           Features: gz-test, default
        Solve group: gz-test
           Channels: https://prefix.dev/robostack-noetic, conda-forge
   Dependency count: 2
       Dependencies: ros-noetic-desktop, ros-noetic-gazebo-ros-pkgs
   Target platforms: linux-64, osx-arm64
    Prefix location: /home/van525/repos/project/.pixi/envs/gz-test

[TedVanderfeen]

pkgs.txt

[TedVanderfeen]

Confusingly, this works fine on osx-arm64.

I had a look at the stack trace and I think this is a weird conflict between Nvidia and Pixi libraries but I'm a bit in over my head on that front. Hopefully someone else can reproduce on linux-64.

[traversaro]

I think this is #513 .

[TedVanderfeen]

Yes I did stumble across that after I logged this issue. Is there any fix to get the noetic gazebo packages to a workable state or is it a substantial amount of work/impossible with the EOL upstream Gazebo?

[traversaro]

Yes I did stumble across that after I logged this issue. Is there any fix to get the noetic gazebo packages to a workable state or is it a substantial amount of work/impossible with the EOL upstream Gazebo?

To be honest, I do not know. I think the first step is test this on the recent rebuild, even without merging we can download the built packages as artifact and install them locally.