crash while running polyscope under WSL
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- computer-graphics, operating-systems
Research direction
Start by reproducing the Python 3.8 Polyscope 1.3.1 ps.init() failure under WSL and inspect src/render/opengl/gl_engine.cpp at lines 1679-1682. Check the reported glfwCreateWindow failure path and the indirect-rendering limitations; done should mean the WSL case no longer crashes and its supported rendering behavior is documented or handled.
Written by the indexing model from the issue text.
Description
A colleague is trying to use Polyscope (via the Python wrappers) under WSL and it crashes in init when indirect rendering isn't disabled (I've been using it under Linux where it works great). The package has just been installed via pip and hence is using version 1.3.1 under Python 3.8.
>>> import polyscope as ps
>>> ps.init()
GLFW emitted error: GLX: Failed to create context: GLXBadFBConfig
GLFW emitted error: Cannot set swap interval without a current OpenGL or OpenGL ES context
This is immediately followed by a crash in glfwSetWindowPos. Running under GDB suggests this crash is unrelated and just due to not checking return of glfwCreateWindow for a nullptr:
These issues seem to be caused by indirect rendering imposing a hard limit of OpenGL version 1.4. This precludes most of the newer features Polyscope requires, hence the GLXBadFBConfig error.
I can create a pull request for the crash, but wondering if anyone has any suggestions about getting it using a GPU under Windows 10?
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 242
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nmwsharp/polyscope
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Rust Version Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in nmwsharp/polyscope
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/message_filters#338 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
subsurface/subsurface#4984 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·