google-deepmind / google-deepmind/dm_control
Segmentation Fault with MuJoCo
- Dominant language
- Python
- Stars
- 4.7k
- Forks
- 764
- PR merge metrics
- No merged PRs in 30d
Description
I'm looking to benchmark both dm_control and MuJoCo.
This
```
import gym
from dm_control import suite
env = gym.make('HalfCheetah-v3')
```
yields
```
Traceback (most recent call last):
File "wrappers.pxi", line 1139, in mujoco_py.cymj.PyMjModel._extract_mj_names
AssertionError
Exception ignored in: 'mujoco_py.cymj.PyMjModel._set'
Traceback (most recent call last):
File "wrappers.pxi", line 1139, in mujoco_py.cymj.PyMjModel._extract_mj_names
AssertionError
Segmentation fault (core dumped)
```
whereas this exits gracefully:
```
import gym
env = gym.make('HalfCheetah-v3')
from dm_control import suite
env = gym.make('HalfCheetah-v3')
```
I'm using
```
dm-control 1.0.1
mujoco 2.1.3
mujoco-py 2.1.2.14
gym 0.21.0
```
While I'm happy to keep using this solution, it feels like a hack and a fix would be much appreciated!
Contributor guide
Research direction
Start by reproducing the import-order difference using the listed dm-control, MuJoCo, mujoco-py, and gym versions. Inspect the failure reported in wrappers.pxi and mujoco_py.cymj.PyMjModel._extract_mj_names, then verify that importing dm_control before gym.make no longer causes an assertion followed by a segmentation fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100