Track memory usage in tests
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 19
- Forks
- 8
- Avg merge
- 6h 41m
- Merged PRs (30d)
- 2
Description
How do we make sure that:
- there are no memory leaks in our code
- everything that needs to be GCed by Ruby has been
- we don't use Ruby objects that have been GCed (
GC.stress=tryecould do the trick, but is slow, see https://github.com/Shopify/liquid-wasm/issues/168. It could be an option we turn on in CI?).
I think we could leverage #18, and measure memory usage during the execution. After a warmup phase, memory usage should be stable.
Maybe we could also measure allocations like in SFR.
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
Start by reviewing issue #18 and the existing test execution flow. Investigate Ruby GC.stress and ways to measure memory usage or allocations during tests, including the SFR approach. Done should include a practical CI-compatible check showing stable memory after warmup and coverage for leaks or unsafe use of GCed objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100