scratchfoundation / scratchfoundation/scratch-blocks
Some projects are severely slow, with very high memory use
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Certain projects became severely slow after the release, with very high memory use; performance dropped significantly compared with before. One repro: open https://scratch.mit.edu/projects/1306151552/editor/ and switch to the "engine" sprite. An extreme case reported around 9.7 GB of memory use.
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 opening the linked Scratch project and switching to the "engine" sprite to reproduce the slowdown and extreme memory use. Read the two linked discussion reports for additional symptoms and reproduction details; done means performance and memory use are substantially restored compared with before the release.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100