The experience is basically the same as working locally, except the linter, language server, formatter, and compilation run on the server-side (and hence don't bog down my laptop in this case). Then they figured out how to make latency and/or network intermittencies a non-issue. The big deal is that vscode uses a client/server setup, where a "client" vscode instance runs on your machine and a "server" vscode instance runs on the remote one. I use vscode-ssh to offload the heavy work to my desktop when working from my laptop. Thank you for bringing this up to my attention and I'm sorry for misunderstanding the initial issue. When running out of sources, those recommendations do not show up and the entire code responsible for those does not execute. The built versions of VS Code offer file type extension recommendations, for example you open a `.php` file and a recommendation comes in to point you to the PHP extension. That is why we believed the issue is about the v8 VM not freeing memory back to the OS when we freed memory logically.īut it turns out I tried the steps again just now, and there is a real memory leak in there! It only reproduces when running a built version of VS Code, such as VS Code Insiders or VS Code Stable. I believed the issue is about the memory usage reported by the OS vs the memory usage reported by the logical JS Heap Snapshot, which is a common topic for garbage collected runtimes, such as JS / v8. ![]() The problem is that I tried to reproduce it back in October while running from sources, and I could not reproduce any leak. ![]() Hi, I'm a developer on VS Code and wanted to clarify that there was actually a logical memory leak in there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |