oblador / oblador/react-native-performance
Are all entries held in memory indefinitely unless cleared manually? When are entries cleared?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 48
- Avg merge
- 1h 6m
- Merged PRs (30d)
- 1
Description
What are the memory implications to using this module without clearing marks/measures? Do entries need to be cleared in production; otherwise memory leaks? What is a typical strategy for clearing marks/measures?
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, test, or entry point is identified in the issue. Inspect the module's mark and measure lifecycle and determine whether entries persist, then document the memory implications and a typical production clearing strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100