You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are submitting a bug report, please fill in the following details and use the tag [bug].
Describe the bug
A clear and concise description of what the bug is.
I was running a customed mujoco environment based on stablebaseline3, and the programme shut down without Error but only warning:
..anaconda3/envs/myenv/lib/python3.7/multiprocessing/semaphore_tracker.py:144: UserWarning: semaphore_tracker: There appear to be 6 leaked semaphores to clean up at shutdown
len(cache))
when debugging, I found that the problem was that when a base64.b64encode() was called to encode a gym.Box object, which is my observation_space, the programme failed without even get inside the base64.b64encode() fuction, so with no furthur info I can't debug no more.
Worth mentioning that such BUG didn't occur when I use another machine. At first I thought it might be the conda environment stuff, so I removed the original environment and create new ones according to the need several times, only to find the same problem still occured. Finally I conda enc export>vital_env.yml the environment from the machine that have no problem, and conda env create -n myenv -f vital_env.yml, and double check the two environments have the same versions on all libraries, however the PROBLEM STILL OCCUR! So I think there is some bugs I don't know.
Code example
Please try to provide a minimal example to reproduce the bug. Error messages and stack traces are also helpful.
base64_encoded=base64.b64encode(cloudpickle.dumps(data_item)).decode()
# data_item is a gym.Box
System Info
Describe the characteristic of your environment:
Describe how Gym was installed (pip, docker, source, ...):
gym=0.21.0 is install thru pip 20.2.4 from a conda command conda env create -n myenv -f vital_env.yml
What OS/version of Linux you're using. Note that while we will accept PRs to improve Window's support, we do not officially support it.
ubuntu 22.04
Python version
python 3.7.10
Additional context
Add any other context about the problem here.
The full env list of my conda enviornment is as below:
I have also installed a custom_envs using pip install -e ./mujuco_environment command and this folder include one of my newly-written environment add to the problem-free envs provided by the original project repo. Howeve, after I mv my self-written environment, and try pip install -e ./mujuco_environment again, and then the problem still occur!
The other problem is that I created a soft link(ln -s) in anaconda3/lib/: libtinfow.so -> libtinfow.so.6.4 and libtinfow.so.6 -> libtinfow.so.6.4, and such warning always occur:
/bin/bash: ~/anaconda3/lib/libtinfo.so.6: no version information available (required by /bin/bash)
would that also be the cause?
Checklist
I have checked that there is no similar issue in the repo (required)
The text was updated successfully, but these errors were encountered:
If you are submitting a bug report, please fill in the following details and use the tag [bug].
Describe the bug
A clear and concise description of what the bug is.
I was running a customed mujoco environment based on stablebaseline3, and the programme shut down without Error but only warning:
when debugging, I found that the problem was that when a base64.b64encode() was called to encode a gym.Box object, which is my observation_space, the programme failed without even get inside the base64.b64encode() fuction, so with no furthur info I can't debug no more.
Worth mentioning that such BUG didn't occur when I use another machine. At first I thought it might be the conda environment stuff, so I removed the original environment and create new ones according to the need several times, only to find the same problem still occured. Finally I
conda enc export>vital_env.yml
the environment from the machine that have no problem, andconda env create -n myenv -f vital_env.yml
, and double check the two environments have the same versions on all libraries, however the PROBLEM STILL OCCUR! So I think there is some bugs I don't know.Code example
Please try to provide a minimal example to reproduce the bug. Error messages and stack traces are also helpful.
System Info
Describe the characteristic of your environment:
Describe how Gym was installed (pip, docker, source, ...):
gym=0.21.0
is install thrupip 20.2.4
from a conda commandconda env create -n myenv -f vital_env.yml
What OS/version of Linux you're using. Note that while we will accept PRs to improve Window's support, we do not officially support it.
ubuntu 22.04
Python version
python 3.7.10
Additional context
Add any other context about the problem here.
I have also installed a
custom_envs
usingpip install -e ./mujuco_environment
command and this folder include one of my newly-written environment add to the problem-free envs provided by the original project repo. Howeve, after Imv
my self-written environment, and trypip install -e ./mujuco_environment
again, and then the problem still occur!The other problem is that I created a soft link(
ln -s
) in anaconda3/lib/:libtinfow.so -> libtinfow.so.6.4
andlibtinfow.so.6 -> libtinfow.so.6.4
, and such warning always occur:/bin/bash: ~/anaconda3/lib/libtinfo.so.6: no version information available (required by /bin/bash)
would that also be the cause?
Checklist
The text was updated successfully, but these errors were encountered: