-
Notifications
You must be signed in to change notification settings - Fork 8.6k
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Bad interaction between mujoco and pytorch #680
Labels
Comments
PR #2762 is about to be merged, introducing V4 MuJoCo environments using new bindings and a dramatically newer version of the engine. If this issue still persists with the V4 ones, please create a new issue for it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code causes a crash:
The crash is in pytorch but I'm reporting it here because it seems to be caused by something gym is doing when initialising mujoco environments. The crash goes away if
import torch
is moved before the call togym.make
, or if thegym.make
call is changed to build a non-mujoco environment. Building other mujoco environments (egInvertedDoublePendulum-v1
) triggers the same crash under the same circumstances.I am using
mujoco-py==0.5.7
withmjpro131
.Output:
The text was updated successfully, but these errors were encountered: