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

reproducer for test suite blowup to hand off to ghc folk

Open
#280 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell

Research direction

Start by reviewing the recently fixed blowup and the proposed Test.Vector.Unboxed module as a candidate reproducer. Build and profile it with ghc master at O1 and O2, comparing reported memory use with observed RAM usage. Done means a small, reproducible case suitable for handoff to the GHC team.

Written by the indexing model from the issue text.

Description

I was talking with @AndreasPK , and a more polite version of the blowup that we fixed recently that can easily be built / profiled with ghc master and has < 3gb memusage would be ideal.

@lehins any thoughts on this? (would a version of Test.Vector.Unboxed module work?)

the pre split into modules blowup had the bizzare extreme ~ 16-17gb ram usage, though ghc would only report using ~ 3-6gb?

current theory: O1/O2 have some space leaks that this code exercises.

Dominant language
Haskell
Stars
401
Forks
145
PR merge metrics
No merged PRs in 30d

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 haskell/vector

All issues in haskell/vector

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.