microsoft / microsoft/vscode-edge-devtools
The extension makes memory usage of Code growing continously and end up crashing.
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):
- VS Code Version: 1.77.3 (Universal)
- OS (e.g., Windows 10): macOS Ventura 13.3.1
- Extension version (e.g., 1.2.3): v2.1.1
Describe the bug:
Memory usage of Code keeps growing and ends up crashing if and only if this extension is enabled.
Repro steps:
- One remote cloud-platform server instance, start a docker container mounting the directory of the source codes.
- Open vs code, with this extension enabled, remotely connect to the server instance, and attaches the container.
- Open 1 or 2 source code files in the editor, and wait, do nothing else.
- After a few minutes, vs code crashes: the window terminated unexpectedly (reason 'crashed' code '5')
Expected behavior:
No crash.
Additional context:
I previously created an issue under Code project, where core dump files could be found.
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
No source file, test, or entry point is named. Start by following the provided remote Docker and VS Code reproduction steps with the listed versions, then use the linked VS Code issue and crash dumps as context; done means the extension no longer causes steadily increasing memory usage or a crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript, vscode
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100