wordpress-mobile / wordpress-mobile/GutenbergKit
Memory leak in `EditorAssetBundleProvider`
Open
Nobody has claimed this yet.
Reader
- Dominant language
- JavaScript
- Stars
- 29
- Forks
- 6
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
I perceive these are never removed/emptied. Is there a memory leak concern? Should we concern ourselves with cleaning these up at some point or is the risk negligible?
Originally posted by @dcalhoun in https://github.com/wordpress-mobile/GutenbergKit/pull/302#discussion_r2737203013
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 locating EditorAssetBundleProvider and tracing the objects referenced in the issue. The payload does not identify files, tests, or a concrete change, so first establish whether the objects are retained and define what cleanup or evidence would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100