[DevTools Bug]: Profiler fail at createing profile for large pages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 251k
- Forks
- 51.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 53
Description
Website or app
My Project
Repro steps
If you have a large enough page the profiler fails to create a profile even for a small time window and the page freezes
I need a way to profile my pages. I think a file output instead of the visualizer can be helpful.
How often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
No response
Error call stack (automated)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
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 reproducing the failure with a sufficiently large page and a short profiling window, then inspect the React DevTools profiler flow involved in creating the profile. Done means profiling no longer freezes the page or fails to create a profile; the issue also suggests evaluating file output as an alternative to the visualizer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- devtools, javascript, react
- Domain
- devtools, frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100