GC Finalization Cycle Warnings
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
Building in debug mode gives a lot of GC warnings when building documentation of Macaulay2Doc. Is this normal? Is it worth investigating when it started?
When building the first time, here is when the first one shows up on my machine:
```m2
-- capturing example results for "Set - Set"
GC Warning: Finalization cycle involving 0x7f9bc3f50a00
```
The addresses that show up are fixed, but I'm not sure how to debug that.
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 debug-mode documentation build for Macaulay2Doc and note when the first finalization-cycle warning appears, during capture of the "Set - Set" example results. No source file or test is named, so begin by locating the documentation build entry point and the warning origin. Done means determining whether the warnings are expected and, if not, identifying when they began and documenting or fixing the cause.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100