OpenLightingProject / OpenLightingProject/open-fixture-library
Investigate memory issues
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 258
- Forks
- 100
- Avg merge
- 11h 52m
- Merged PRs (30d)
- 53
Description
E.g. when running the http-status test against the local development deployment, the server eventually runs out of memory. With each request, the total amount of used memory increases. The same applies to the production server, but the memory growth is a bit smaller there so the memory limit isn't reached when running http-status.
It needs to be investigated whether we can fix a memory leak in our code and prevent our server from collapsing if there are too many requests.
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 memory growth with the http-status test against the local development deployment, then compare it with production as described. Trace memory usage across repeated requests to identify whether the leak is in project code. Done means the leak is fixed and the server no longer collapses under too many requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100