Add a troubleshooting section in TROUBLESHOOTING.md for memory issues #443
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RenFraser
approved these changes
Mar 24, 2023
fwcd
reviewed
Mar 28, 2023
themkat
changed the title
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Several people have been experiencing memory issues with the language server for their projects. While this PR doesn't fix anything, I think it can be useful to point people to something they can try to possibly fix the issues on their machines. Therefore I suggest adding a troubleshooting section to the README so it is visible somewhere. Feel free to suggest a better place 🙂
The vscode description depends on fwcd/vscode-kotlin#121
Issues: #441, fwcd/vscode-kotlin#120 , #403.