vscode
vscode copied to clipboard
microsoft
Vs code takes up a lot of RAM storage
Type: Performance Issue
Some days is that I run my VS CODE and writting my code after that I check the task manager and my vs code take a lot of RAM almost 4 Gb or higher and my VS CODE get lags. Why that problem happend? I checked my extentions in my freind lap top but she hasn't that problem, please help me to sovle it.
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z) OS version: Windows_NT x64 10.0.19045 Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 5 4600H with Radeon Graphics (12 x 2994) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.36GB (6.68GB free) |
| Process Argv | C:\Users\HP\Desktop\client --crash-reporter-id 946e69aa-f78e-4b37-9d01-b191dc72f993 |
| Screen Reader | no |
| VM | 0% |
Extensions (6)
| Extension | Author (truncated) | Version |
|---|---|---|
| simple-react-snippets | bur | 1.2.7 |
| es7-react-js-snippets | dsz | 4.4.3 |
| prettier-vscode | esb | 10.1.0 |
| auto-rename-tag | for | 0.1.10 |
| vscode-extension-auto-import | Nuc | 1.4.3 |
| material-icon-theme | PKi | 4.32.0 |
The performance wiki (https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-is-consuming-a-lot-of-cpu) has some tips how you can find out who is using that much memory. Can you follow these steps?
The performance wiki (https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-is-consuming-a-lot-of-cpu) has some tips how you can find out who is using that much memory. Can you follow these steps?
Thank man, I will check it later.
Hey @aeschli, this issue might need further attention.
@MohammadGlp, you can help us out by closing this issue if the problem no longer exists, or adding more information.
