Roslyn: error MSB6006: "csc.dll" exited with code 137

[livarcocc]

@khteh commented on Thu Oct 10 2019

Steps to reproduce

Expected behavior

Actual behavior

Environment data

dotnet --info output:

$ dn --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  19.04
 OS Platform: Linux
 RID:         ubuntu.19.04-x64
 Base Path:   /usr/share/dotnet-3.0.100/sdk/3.0.100/

Host (useful for support):
  Version: 3.0.0
  Commit:  7d57652f33

.NET Core SDKs installed:
  3.0.100 [/usr/share/dotnet-3.0.100/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet-3.0.100/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet-3.0.100/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

[gafter]

Please provide the source files and a build script that demonstrates the failure.

[khteh]

Reply from CircleCI:

Exit code 137 typically means that your process is getting killed because it is running out of memory.

Could that point to potentially memory leak in the toolchain?

[khteh]

I have 33 projects in the .sln. I can build the .csproj individually without the error MSB6006.

[SohamJadiya]

Hey Did anybody solved this error?
Because I am getting the same error whilst trying to build nopcommerce on centos with dotnet.

[adebelyi]

Hey Did anybody solved this error?
Because I am getting the same error whilst trying to build nopcommerce on centos with dotnet.

How much RAM do you have?
In my situation after restarting the server everything was ok. After some time, build was falling with this error until I restart the server.

[hasancemcerit]

This exact same error occurs on my TeamCity build agent that runs on Ubuntu as well.

My observation is that I have sonarqube analyzer step enabled when this error in dotnet build occurs.
If I disable that step, I haven't encountered the error. 🤔

Although I watched the memory usage while the build is running and it didn't peak, I also think it might be something to do with memory.