Freeze on loading project in wsl 2
已回答
Tried disabling all plugins, I keep getting a freeze when loading wsl2 projects with some kind of error like this in the logs:
'Permission denied (os error 13), path: /dev/sg1'
Logs here: Upload id: 2022_08_13_ULDCYTtmFSb86dPBvZR3Xd (files: idea.log and 3 more)
请先登录再写评论。
The symptoms suggest that you may be affected by this issue, which was fixed in version 2021.3 of IntelliJ IDEA. If you use an older version, we recommend updating to benefit from this and other bug fixes.
If you can't update for some reason, this workaround might help:
I still see this happening on the latest IntelliJ build (2022.2.2).
Turning off wsl.fsd.content.loader did the trick!
wsl fsd no longer helps on windows 11
only disable Windows Defender real time protection. Nothing else work, no exclusion folders doesn't work also.
https://github.com/microsoft/WSL/issues/8995
I am having the same problem and can confirm turning off Defender addresses it.
Same log segments I posted on that thread.
I have the exact same problem, and can confirm turning off Defender takes care of it, but really don't consider that a solution.
Logs before disabling defender:
Same issue here. IntelliJ, PyCharm, all with the same issue. Projects created in the WSL2 filesystem are excruciatingly slow to open in the IDE. It's unworkable. This only happens since the upgrade to Windows 11, no issues with Win10.
Is there any solution for this? (Disabling Windows Defender protection is not a solution, for obvious reasons, and I really don't want to switch to VS Code)
Lshem16 Pedro Anastacio
See if it helps to add everything related to the IDE to the Defender's exclusions (see this comment for the guides): idea process, default directories, project folder, etc. People reported that it helped, even on Windows 11.
@... Thanks for the suggestion. However, that didn't solve the issue. I've excluded the processes, default directories, etc... but to no avail.
I confirm that disabling the real-time protection makes everything work as expected, though. But as stated previously, having to disable that is not a solution at all.
Pedro Anastacio, please, try to perform the following workarounds:
wsl.fsd.content.loader=falseinHelp | Edit Custom Propertiesand restart the IDE.If it doesn't work, please, make a request via our form and attach your IDE logs.
Hello Olga Mulina I tried this 2 some time back it didn't change anything
the wsl.fsd.content.loader do changed something but still for my project I was not able to open it... its a pretty big project have to say.
So the only REAL workaround is to TURN off the defender antivirus.
It is even weirder to be fair, even if it is turned off.. if I restart my IntelliJ IDEA several times sometimes it stuck but enable real time protection and disable it again always fixes the issue.
I am using nowadays a Windows shortcut... it starts when Windows starts and if I have any issue I just run it again prior to opening IntelliJ IDEA it might be handy for some people here, just create a shortcut and in target type:
This is it.
This is the list of excluded folders I have... it didn't help... only turn off real time protection works. The last folder z:\wsl is the folder where I have both Ubuntu and OpenSuse
We created a YouTrack ticket about this problem to investigate it and find a possible solution/workaround, you can upvote and follow it to receive updates. Our developers will review it soon.
FYI, nearly a month later and still no solution for this. A month unable to use Jetbrain tools in Windows 11. So disappointed.
Please see https://github.com/microsoft/WSL/issues/8995. Disabling real-time antivirus protection is the only known workaround so far. We don't know why Microsoft still didn't fix this issue.
I'm observing that issue. What puzzles me is that VS Code (and other IDEs) has no issues on Win11 and WSL2, so telling us that it's exclusively an issue on Microsoft side seems an easy way out for you.
These tools work differently. VS Code server runs directly inside the WSL, while IntelliJ IDEA accesses the files inside WSL which is affected by the antivirus. Antivirus should not affect I/O performance when proper exclusions are set up which is not the case with Windows 11 for some reason.
You can use IntelliJ IDEA in the same mode as VS Code (server inside WSL and client on Windows) which should work faster when I/O performance is killed by the AV:
On the Welcome Screen use Remote Development | WSL option.
Confirmed again the issue is still present and Windows Security exclusions still do not work. Has anyone tried reaching out to Microsoft? They're ignoring the bug linked here. I figure official JetBrains people may have more sway than us common folk
Just to confirm I do not think IntelliJ will be able to fix this issue ever. So @Pedro Anastacio I would suggest to not expect a fix.
For now there are 2 easy fixes.
One is to use REAL TIME PROTECTION turn off always when you start your windows. I am using a powershell shortcut that does this:
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe Set-MpPreference -DisableRealtimeMonitoring $true"
The issue with this is that sometimes the real time protection is automatically turned on after a 12+ hours of startup. Also sometimes the real time protection is shown as OFF but in fact is ON so you have to click it OFF/ON again.
There is a not very well known workaround - Installing ANY ANTIVIRUS will TURN OFF the real time protection. I just installed the free version of AVAST to get rid of this Microsoft virus called Windows defender. Now all works I don't have to disable or enable anything, always, on every restart and no need for power shell or on off mambo jambo.
Well, at least the tip for installing a new antivirus seems to be something more reasonable than the "we cannot solve the issue" or "disable the computer security".
However, I would emphasize the comment from Lshem16: Jetbrains refer us to the GitHub issue opened on the WSL repo, but we can't see any interaction there from any Jetbrains responsible. It just seems that no one, Microsoft nor Jetbrains, seems to be interested in solving this.
As @... I confirm that installing a different AntiVirus solves the issue