microsoft / microsoft/vscode-edge-devtools
High CPU and janky experience while using Edge Tools Screencast
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 358
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
Environment (please complete the following information):
- MacOS 12.3
- 15" Macbook Pro (2017)
- VS Code: 1.65.2
- Edge dev tools v1.4.5
Describe the bug:
I just cloned this repo and while playing around with the edge dev tools / debugger, I'm noticing high CPU rates. Especially so when the screencast is in view. Navigating the sample app is quite janky / unresponsive. This has a massive impact on the overall experience of using the screencast.
Repro steps:
Clone https://github.com/codepo8/simple-to-do, open vscode and start debugger with http-server
Expected behavior:
For the overall experience to feel snappy without high cpu levels
Additional context:
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
Reproduce the issue by cloning the linked simple-to-do repository, opening it in VS Code, and starting the debugger with http-server. Compare CPU usage and responsiveness with the Edge Tools Screencast visible and hidden. Done means the sample app feels responsive during navigation without the reported high CPU usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100