Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

There seems to be some sort of weird bug using Polyscope and MSVC (bug from the CMU DDG course)

Open
#238 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

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.

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:
273365619-2929ce2e-21bc-42ef-b653-5953d4a81023

The problem seems to be related to MSVC

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nmwsharp/polyscope

All issues in nmwsharp/polyscope

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.