Investigate potential memory leak
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 41
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 16
Description
- Open streaming example
- Click
Load moreon page - Open DevTools
Take heap snapshoton Memory tab- Click
Load moreon page Take heap snapshoton Memory tab- Click on
Snapshot 2and filterObjects retained by detached DOM nodes - See also
Objects allocated between Snapshot 1 and Snapshot 2
Also, open Performance monitor and click Start on page to stream data and watch the fluctuations on JS heap size (with GC kicking in, but still a general upward trend). More notable, see the large / consistent increase in DOM nodes .
See discussion
Investigated streaming performance a few weeks ago when using Canvas and substantially improved the issue, but wasn't able to 100% resolve the issue.
Contributor guide
No contributing guide indexed for this repository
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 with the linked streaming example and reproduce the issue using DevTools Memory and Performance monitor. Compare heap snapshots after successive Load more actions, filtering detached DOM nodes and objects allocated between snapshots, while observing JS heap size and DOM nodes during streaming. Done means identifying the retention cause and demonstrating that the upward memory and DOM-node trend is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100