nextcloud / nextcloud/whiteboard
Profile browser memory usage
Open
Nobody has claimed this yet.
1. to develop
need to reproduce
performance 🚀
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
While doing some load testing there was a mention by @provokateurin that the browser is using 3GB ram for the single tab.
Some things to clarify:
- What browser was used?
- Was it within the talk call or just the files app?
Most important: Can we reproduce, investigate and improve?
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
No files, tests, or entry points are named. First establish which browser was used and whether the memory use occurs in a talk call, the files app, or both, then reproduce it under load testing. Done means identifying the cause and demonstrating reduced browser memory usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100