There seems to be some sort of weird bug using Polyscope and MSVC (bug from the CMU DDG course)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 242
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
So I tried the following on my PC (W11, Visual Studio 2022) and on my workplace's (W10, Visual Studio 2017)
When I cloned the dgg-exercises repo from scratch and built and ran the vector-field-decomposition project, the program would suddenly abort upon calling polyscope::show()
Here's the callstack produced:
The problem seems to be related to MSVC
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.
Research direction
Reproduce the failure by cloning the dgg-exercises repository and running the vector-field-decomposition project on Windows with MSVC, then inspect the call stack from the abort at polyscope::show(). Compare behavior between Visual Studio 2022 and 2017; done means identifying and fixing the MSVC-specific cause so the project runs past polyscope::show().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100