Possible memory leak in decode function?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
we are using a library which depends on version 0.1.5. We noticed a heavy memory increase in our application and started debugging it via node profiler. After getting some snapshots, we noticed a big JSArrayBufferData object which contains a call to the decode function of the @cwasm/webp package. The object never gets collected by garbage collector, even when we force a cleaning via global.gc().
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 at the package's decode entry point and reproduce the memory growth with version 0.1.5 while inspecting profiler snapshots. Compare behavior before and after forcing global.gc(), focusing on whether JSArrayBufferData remains retained. Done means the retained buffer is collected and the memory increase is no longer observed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, wasm
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100