WSL2 settings recommendation added #1628
Conversation
|
We probably should make a comment somewhere (although I don't think this belongs in the RST) that there is a very long standing bug in WSL2 for Windows 10&11 that enduces a memory leak and cpu hogging. This happens when you have WSL open and lock your PC. If you log back in and resume your session the leak starts to manifest (as far as I can remember) The fix is to shut it down and restart I will search the coming days if I can find the discussion / issue that I'm refering to. |
|
The created documentation from the pull request is available at: docu-html |
What level of detail is targeted in this documentation? Is it intended to be short, or can it be more comprehensive? If it is more comprehensive, we could add hints on bugs or add additional information (e.g. how to connect to WSL from the IDE). That could feel too chatty for experienced developers, but might be helpful for less experienced people working on the project. As we use X-as-Code, we could expect that people who are actually used to other, "non-code tools" would work here, too. What do you think? |
|
|
||
| WSL2 Settings | ||
| ============= | ||
| If you are using a Linux box running on WSL2, the following minimal settings in your .wslconfig file are recommended: |
There was a problem hiding this comment.
Maybe we can rephrase this and merge, so we don't need to wait for @MaximilianSoerenPollak? Currently it's difficult to tell when out-of-memory happens, as no-one has complained yet. I assume memory becomes an issue when you run an (old) C++ linker?!
| If you are using a Linux box running on WSL2, the following minimal settings in your .wslconfig file are recommended: | |
| If you encounter memory issues on WSL2, the following minimal settings in your .wslconfig file are recommended: |
There was a problem hiding this comment.
The settings do not solve this issue. So to speak, once the leak happens and stays for a while the performance goes into the tank, even if it stays inside the parameters.
But I do think we should have some sort of short info that one can set such settings?
There was a problem hiding this comment.
We have the info about settings here. Info about the leak we can publish once people start complaining :)
I think the detail you have is good, I wouldn't go too into detail imo. |
Description
Added a short recommendation how to put settings for WSL2.