microsoft / microsoft/ntttcp-for-linux
Address memory leak issues in the code where resources are not freed
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 426
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Received the Copilot comment on my PR #104. I have created it as a different issue, and I will take it up later.
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 PR #104 and the Copilot comment that prompted this issue, then locate the resource-management paths implicated there. Done means the identified resources are freed correctly and the memory leak is no longer reproducible; the issue names no specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100