Tutorial Colab raises GLEW initalization error when rendering
See original GitHub issueThe tutorial colab notebook crashes as soon as rendering is called:
from dm_control import suite env = suite.load('cartpole', 'swingup') pixels = env.physics.render()
The following error rises:
CRITICAL:absl:GLEW initalization error: Missing GL version
I tried different instances with and without GPU. After some research through the issues here and https://github.com/openai/mujoco-py/issues/268, I still wasn’t able to solve it.
Thanks for your help.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
How to Fix Google Colab and Blender CUDA Errors - YouTube
In this Blender and Google Colab tutorial, I will be showing you how to fix two common errors reported by viewers.
Read more >GLEW initalization error: Missing GL version - Roboti LLC
Ideally I would link both glew and glfw statically. But people want multiple off-screen rendering options (and sometimes no rendering at all) so ......
Read more >Changelog - MuJoCo Documentation
The Renderer class from the MuJoCo tutorial Colab is now available directly in the native Python bindings. General . The tendon springlength...
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild ... Bug:111508 - "Adding the examples USE flag to packages installing example source...
Read more >LANGUAGE SUPPORT FOR RELIABLE, EXTENSIBLE ...
for null and potentially raise an exception that will crash the program. ... This example is simple, but in general, initialization bugs are...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m glad that works for you. It does mean that you’d be sharing the GPU if you’re using it for training/inference as well as rendering, which may or may not be a bad thing. I will leave this issue open anyway, since we should ideally support non-hardware rendering as well.
Thanks, that is useful information - I am able to reproduce the problem. I am not yet sure what has changed, as this certainly used to work on cloud kernels. Can you run a local kernel as a temporary workaround?