google / google/tamperchrome

Don't keep editor bodies in memory

Open
#177 0 comments 0 reactions 0 assignees View on GitHub
diff:hard p:child type:enhancement
Dominant language
TypeScript
Stars
4.2k
Forks
232
PR merge metrics
No merged PRs in 30d

Description

This issue has no description.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points and provides no further context. Start by locating how editor bodies are retained, then inspect any related memory tests or profiling guidance. Done should be defined by a verified approach that avoids keeping unnecessary editor bodies in memory.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools, performance
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.