Completely unload dweets that are outside the screen
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 803
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Even though dweets stop running, they still fill up memory, after scrolling through a couple I easily hit 1GB memory usage on a dwitter tab. Solution would be to free/unload dweets after they have been scrolled away from (say 2 dweets out of screen)
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
No file or test is named. Start by tracing how dweets are executed and how scrolling determines which dweets are on screen; measure memory while scrolling. Done means dweets kept outside the stated viewport buffer no longer consume their running resources and still behave correctly when revisited.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100