Possible memory leak in subscriptionClient.errCache
Open
Nobody has claimed this yet.
severity/minor
type/bug
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
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
Start by reading logservice/logpuller/subscription_client.go around line 1133 and trace how errCache is created, updated, and released. Use a memory profile or focused reproduction to determine whether the cache retains entries unexpectedly; done means the leak is confirmed or ruled out with supporting evidence and a regression check if appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100