Skip to content

Mutex assertion crash - gzserver #554

Closed
Closed
Mutex assertion crash - gzserver#554
Labels
bugSomething isn't working

Description

@TedVanderfeen
TedVanderfeen
opened on Oct 16, 2025

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

Activity

  1. TedVanderfeen
    added
    bugSomething isn't working
    on Oct 16, 2025

  2. TedVanderfeen commented on Oct 16, 2025

    @TedVanderfeen
    TedVanderfeen
    on Oct 16, 2025
    ContributorAuthor

    pkgs.txt

  3. TedVanderfeen commented on Oct 16, 2025

    @TedVanderfeen
    TedVanderfeen
    on Oct 16, 2025
    ContributorAuthor

    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.

  4. traversaro commented on Nov 1, 2025

    @traversaro
    traversaro
    on Nov 1, 2025
    Member

    I think this is #513 .

  5. TedVanderfeen commented on Nov 3, 2025

    @TedVanderfeen
    TedVanderfeen
    on Nov 3, 2025
    ContributorAuthor

    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?

  6. traversaro commented on Nov 3, 2025

    @traversaro
    traversaro
    on Nov 3, 2025
    Member

    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.

  7. gavanderhoorn commented on Feb 26, 2026

    @gavanderhoorn
    gavanderhoorn
    on Feb 26, 2026

    @traversaro: I'm running into this as well.

    I think the first step is test this on the recent rebuild [..]

    how recent should that be? And where would that build come from?

    Edit: apologies. I'm not on Noetic, but Humble. I'll comment on RoboStack/ros-humble#265, as in your RoboStack/ros-humble#265 (comment) there, you mention the exact assertion error I'm seeing as well.

  8. Tobias-Fischer commented on Mar 17, 2026

    @Tobias-Fischer
    Tobias-Fischer
    on Mar 17, 2026
    Collaborator

    @TedVanderfeen - can you please try again with the newest builds?

  9. TedVanderfeen commented on Mar 18, 2026

    @TedVanderfeen
    TedVanderfeen
    on Mar 18, 2026
    ContributorAuthor

    @Tobias-Fischer still getting this error. What package versions can I check to see if I actually pulled in the newest builds?

    process[gazebo_gui-3]: started with pid [1415874]
[ INFO] [1773807851.034297096]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1773807851.035087422]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1773807851.125009216]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1773807851.127481711]: 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_gui-3] process has died [pid 1415874, exit code 134, cmd /home/van525/repos/robostack/.pixi/envs/noetic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/ted.ros/log/4f99e3f0-2282-11f1-9500-cc96e5467053/gazebo_gui-3.log].
log file: /home/ted/.ros/log/4f99e3f0-2282-11f1-9500-cc96e5467053/gazebo_gui-3*.log
Aborted (core dumped)
[gazebo-2] process has died [pid 1415871, exit code 134, cmd /home/van525/repos/robostack/.pixi/envs/noetic/lib/gazebo_ros/gzserver -e ode worlds/empty.world __name:=gazebo __log:=/home/ted/.ros/log/4f99e3f0-2282-11f1-9500-cc96e5467053/gazebo-2.log].
log file: /home/ted/.ros/log/4f99e3f0-2282-11f1-9500-cc96e5467053/gazebo-2*.log

  10. TedVanderfeen commented on Mar 18, 2026

    @TedVanderfeen
    TedVanderfeen
    on Mar 18, 2026
    ContributorAuthor

    Nevermind got it. Looks like I pulled ros-distro-mutex - 0.6.0 and not 0.7.0 as per #557

    Will manually pin and retest.

    edit: Doesn't look like ros-distro-mutex == 0.7.0 is available on Conda-forge yet:

    Error:   × failed to solve requirements of environment 'noetic' for platform 'linux-aarch64'
  ├─▶   × failed to solve the environment
  │   
  ╰─▶ Cannot solve the request because of: No candidates were found for ros-distro-mutex ==0.7.0.

  11. TedVanderfeen commented on Mar 18, 2026

    @TedVanderfeen
    TedVanderfeen
    on Mar 18, 2026
    ContributorAuthor

    Switched my channel from robostack-noetic to robostack-staging (thanks @Tobias-Fischer) and it looks like the mutex problem has gone away, but has been replaced with an even less descriptive error message...

    process[gazebo-2]: started with pid [1429156]
process[gazebo_gui-3]: started with pid [1429159]
[INFO] [1773809132.199942360]: Finished loading Gazebo ROS API Plugin.
[INFO] [1773809132.200610041]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[INFO] [1773809132.273507868]: Finished loading Gazebo ROS API Plugin.
[INFO] [1773809132.274196544]: waitForService: Service [/gazebo_gui/set_physics_properties] has not been advertised, waiting...
[INFO] [1773809132.302416945, 0.001000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[INFO] [1773809132.310394130, 0.009000000]: Physics dynamic reconfigure ready.
Aborted (core dumped)
[gazebo_gui-3] process has died [pid 1429159, exit code 134, cmd /home/van525/repos/robostack/.pixi/envs/noetic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/van525/.ros/log/4b48bd82-2285-11f1-9cc4-cc96e5467053/gazebo_gui-3.log].
log file: /home/van525/.ros/log/4b48bd82-2285-11f1-9cc4-cc96e5467053/gazebo_gui-3*.log

  12. TedVanderfeen commented on Mar 18, 2026

    @TedVanderfeen
    TedVanderfeen
    on Mar 18, 2026
    ContributorAuthor

    Alright this looks to be fixed now. But I'll need to wait until I'm sitting back at my linux machine tomorrow to fully confirm.

    The crash in the previous message was just (1773809425 78140451) [Err] [RenderEngine.cc:749] Can't open display:, but I am testing this through a remote/ssh session.

    When I run roslaunch gazebo_ros empty_world.launch gui:=false it doesn't core dump and seems to start up just fine.

  13. TedVanderfeen commented on Mar 18, 2026

    @TedVanderfeen
    TedVanderfeen
    on Mar 18, 2026
    ContributorAuthor

    Yep, all fixed! Thanks for your mammoth efforts in getting all those build conflicts for 0.7.0 resolved @Tobias-Fischer @traversaro!

  14. TedVanderfeen
    closed this as completedon Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions