When running Debian 13 arm64 inside proot-distro on Android/Termux, Visual Studio Code works normally, but opening a .NET project triggers a reproducible failure.
When the C# extension or C# Dev Kit tries to download required components (RoslynCopilot, Razor, .NET runtime, etc.), the download process fails with:
EFAULT: bad address in system call argument, write
Failed at stage: touchBeginFile
This happens consistently and prevents the C# extension from completing its setup.
The same setup works correctly on a real Debian installation (non-proot), so the issue appears to be specific to proot’s syscall emulation when Electron/Node embedded processes perform small, frequent writes.
I am attaching the full VS Code log file showing the EFAULT errors, including:
output.log
When running Debian 13 arm64 inside proot-distro on Android/Termux, Visual Studio Code works normally, but opening a .NET project triggers a reproducible failure.
When the C# extension or C# Dev Kit tries to download required components (RoslynCopilot, Razor, .NET runtime, etc.), the download process fails with:
EFAULT: bad address in system call argument, write
Failed at stage: touchBeginFile
This happens consistently and prevents the C# extension from completing its setup.
The same setup works correctly on a real Debian installation (non-proot), so the issue appears to be specific to proot’s syscall emulation when Electron/Node embedded processes perform small, frequent writes.
I am attaching the full VS Code log file showing the EFAULT errors, including:
output.log