You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was ported from microsoft/vscode/issues/50280 , recently closed with claims that the problem lies here. Please refer to that issue for more information and troubleshooting.
If a Java project is left open for an extended period of time (days), the Java process continues to eat memory, eventually running the machine out of memory and causing swaps on the hard drive. This memory usage is not properly reported by VS Code's metrics nor the Windows Task Manager. This is particularly dangerous because memory continues to be consumed even when just sitting idle - I can leave my computer on with VS Code running with barely any memory usage, and come back a day or so later to my computer swapping away. The only way I've found to free the memory is to restart VS Code, at which point the memory gets released. Here's a screenshot of my task manager as this happens (note the maxed memory and high hard drive activity before VS Code is closed):
While troubleshooting in the original issue, I ran code --status in this condition, and saw the following results:
This was ported from microsoft/vscode/issues/50280 , recently closed with claims that the problem lies here. Please refer to that issue for more information and troubleshooting.
If a Java project is left open for an extended period of time (days), the Java process continues to eat memory, eventually running the machine out of memory and causing swaps on the hard drive. This memory usage is not properly reported by VS Code's metrics nor the Windows Task Manager. This is particularly dangerous because memory continues to be consumed even when just sitting idle - I can leave my computer on with VS Code running with barely any memory usage, and come back a day or so later to my computer swapping away. The only way I've found to free the memory is to restart VS Code, at which point the memory gets released. Here's a screenshot of my task manager as this happens (note the maxed memory and high hard drive activity before VS Code is closed):
While troubleshooting in the original issue, I ran
code --status
in this condition, and saw the following results:Another user had suggested that we inspect the number of process handles to locate the offending process, and here's what Task Manager reported:
I can't provide much more information at the moment, but can collect more if instructed how.
Environment
Steps To Reproduce
The text was updated successfully, but these errors were encountered: