We should take another look at ways we can reduce in memory usage with the extension without harming functionality. Consider the technical stack as well as potential optimizations specifically for VS Code extension, or consider whether there are any memory leaks, etc. Please make a plan and then evaluate without actually implementing any changes. We instead want to get an idea of what resource the extension is using the most and evaluate areas for the improvement, as well as measure how much memory we're currently using. This can be compared by running the test or .NET Install Tool extension with a host vscode instance vs running it when that extension fails to activate.
We should take another look at ways we can reduce in memory usage with the extension without harming functionality. Consider the technical stack as well as potential optimizations specifically for VS Code extension, or consider whether there are any memory leaks, etc. Please make a plan and then evaluate without actually implementing any changes. We instead want to get an idea of what resource the extension is using the most and evaluate areas for the improvement, as well as measure how much memory we're currently using. This can be compared by running the test or .NET Install Tool extension with a host vscode instance vs running it when that extension fails to activate.