Custom Config Loader seems to leak memory
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
Description
We were trying the new config_loader option by passing a lambda, but we see that the Resident Set Size (RSS) of the resque-pool doubles within an hour. When we start the resque-pool, the size was around 500MB but within an hour, the size is above 1G. Without using the config_loader, the RSS remains stable (around the initial size). It seems like whatever object that was created/used within the lambda block is not being GCed.
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 reproducing the resque-pool RSS growth with a lambda passed through config_loader, comparing it with a run without that option. Then trace how config_loader retains or invokes the lambda and use memory measurements to identify the retained object; done means RSS remains stable under the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100