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
SIGSEGV on env.step for multiple renderings. #77
Comments
Hi Chase. I think this is an issue related to the PyQT renderer. Can you provide a code snippet to reproduce the issue? |
Hey thanks for the quick response. Here's where I've instantiated multiple envs: import gym env0 = RGBImgObsWrapper(gym.make("MiniGrid-Empty-Random-5x5-v0")) ######################################################################### And here's where I'm rendering each environment to initialize them into replay buffers:
######################################################################## Thanks again for looking into it. I'll look up the issue in ref to PyQT in the meantime. |
One temporary fix that could work is to run the environments in forked processes. Otherwise though, next week I will start looking at implementing a renderer based on NumPy (see #76). I would ideally like to eliminate the PyQT dependency. You're not the only one to run into issues. If you're available to help me test next week that could he useful :) |
Hey, thanks that's awesome. I'd be happy to help, though I'm working on the implementation so it will definitely not be bug-free. If it's still helpful though, that would be great! |
Hi @chasebos91. I have the new version of MiniGrid that uses NumPy to produce graphics on a new branch |
So far so good! Will let you know as I keep working on it. Thank you!! |
You can access it by first doing a git pull, then:
Then to install the package in editable mode:
|
This is now pushed to the master branch as well :) |
Hey there,
I'm experiencing a segmentation fault after I call env.step when there are multiple renderings open. I saw a closed thread on openai for the same issue, but I'm unsure if the bug still persists across some of their environments.
The text was updated successfully, but these errors were encountered: