Performance issues in Chrome since 142
Open
Nobody has claimed this yet.
bug
feature: frontend 🖌️
high
performance 🚀
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Memory usage
- Up to 2 Gb RAM in Chrome accumulated during ongoing call
- Detached nodes left after hovering elements (chat messages, video tiles, call grid)
- Possible references for peers / streams are kept and not collected by GC
Expensive operations
- mouseover event listeners on elements (chat messages, video tiles, call grid)
- RecycleScroller - using GPU for rendering virtual list
- NcActions - a lot of recalculations (from composables)
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 identified. Start by reproducing the Chrome 142 behavior during an ongoing call, then investigate memory growth, detached nodes, retained peer or stream references, mouseover listeners, RecycleScroller rendering, and NcActions recalculations; done requires measured improvements for the reported problems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, frontend, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100