Filed under:
https://vanillawebdev.blogspot.com/2025/09/auto-open-project-folder-devtools.html
https://vanillawebdev.blogspot.com/2025/09/auto-open-project-folder-devtools.html?max-results=20
https://vanillawebdev.blogspot.com/
user_r100
//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizihHpchmJoGeEVuJGCATZpHw9BgxolQLkV-Mw0hXTuIjdZQ8e_AeFQZdY6r5UrGWerl4b3Qx4aYsVx2w9y474FJvlyZDZiNcCLLNNQly7M3NZ8Xz1g2dsxQh3yuQJln2e6JTJtzci506US-j64gEDelPT-QYo7_TFH1kTp6AapPzrZQ/s220/channels4_profile.jpg
6059206262860954295
https://vanillawebdev.blogspot.com/2026/03/vs-code-memory-usage-in-chromeos.html
VS Code Memory Usage in ChromeOS
March 31, 2026
2026
March
31
04:49 PM
VS Code is very slow on my 4GB RAM Chromebook, but I need the diff tool to commit changes on a project. So I wonder what if I just open it in the background and use vscode.dev for the coding?
Linux VS Code use around 400MB of RAM. While on idle, my Chromebook already takes up 3GB RAM, so it doesn't show any noticeable difference in system performance, except for the initial application load.
CPU usage spikes to 100% when opening VS Code. It quikly stabilize after few seconds.
 |
I haven't noticed it before, but apparently my Chromebook always runs on 3/4 RAM usage.
 |
https://www.blogger.com/rpc_relay.html https://www.blogger.com/comment/frame/8166404610182826392?po=6059206262860954295&hl=en&saa=85391&origin=https://vanillawebdev.blogspot.com&skin=contempo https://vanillawebdev.blogspot.com/2026/03/vs-code-memory-usage-in-chromeos.html#comments https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqNaxlklisumgQPLxT5IxG12gYagx7BA68gJLG4WVBE9ob_g_FhW-MJU6sILffwjrkaNiiw8gGQc0U5cvMEuauJY8P3rKW36UEZdGv2O40rTEnbgg5aBEF66oNtsQpCzBZWaFYssmry0Nh7n0DfEY_WoKf3HXpYOLZnoTByIC9bybjEVkW5fIQPq1xsWTV/s72-c/chromeos-memory-usage-vscode.png ]
https://vanillawebdev.blogspot.com/2025/09/auto-open-project-folder-devtools.html
https://vanillawebdev.blogspot.com/