![]() Granted it does look there could be a bug as the number of sockets seems to steadily rise, but maybe that's because these processes are exiting incorrectly in the first place (so it's a symptom rather than the cause). I swear this had gotten worse since upgrading to v0.61.4/5 but that might just be would it be possible to get some eyes on this? (or a comment saying that eyes have been on it) It's a real barrier to being able to comfortably use JetBrains products on WSLv2, and so far I've not seen a lot of hope that this will get improved or fixed.Įveryone over on IDEA-276250 seems to think that #7883 is the problem behind this, which you said a fix was being rolled out yet this problem remains I also don't actually see a strong connection between this issue and that one (for one it's about Windows programs hanging inside WSL when I'd expect IntelliJ to be calling WSL programs from Windows + hanging wouldn't cause an exit code of 1 since by definition there is no exit) so am not sure why people are thinking this is the same issue.Įveryone keeps suggesting removing the interop sockets in /run/WSL but I again have not seen any solid explanation on why that is believed to be the problem and it doesn't actually fix the problem - I get this when I have ~100 old sockets, I get this when I have ~900 old sockets, and clearing out the sockets appears to have a minimal effect if any (definitely not enough to rule out correlation vs causation) not to mention that the clearing out breaks the ability to invoke Windows commands for all current processes (like terminals).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |