rubyforgood / rubyforgood/casa
Bug: Memory Leak
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
Impacted User Types
Tech Leads
Environment
production
Current Behavior
The rise after the restart probably comes from people using the app at 10PM. But the memory usage keeps climbing well after users go to sleep.
How to access the QA site
Login Details:
Link to QA site
Test Environment Login Emails:
- volunteer1@example.com view site as a volunteer
- supervisor1@example.com view site as a supervisor
- casa_admin1@example.com view site as an admin
- all_casa_admin1@example.com view site as an all casa admin
- go to
/all_casa_admins/sign_in
- go to
password for all users: 12345678
Questions? Join Slack!
We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.
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 reported memory growth on the QA site at https://casa-qa.herokuapp.com/, using the listed sign-in routes and user roles while monitoring usage over time. No source file or test is named, so trace the production behavior to the responsible application area and document a reproducible case; done means memory no longer keeps climbing after activity stops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100