AsyncBaton may leak memory if an error occurs in shave setup
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 44
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Per @springmeyer 's thoughts:
We should use the RAII pattern to ensure that AsyncBaton will not leak if an exception occurs.
Contributor guide
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
Locate AsyncBaton and the shave setup entry point, then trace what happens when setup raises an exception. Identify the existing tests for setup or error handling and use them to define done: AsyncBaton resources are released on the error path without changing successful setup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100