Hi,
I have a problem when trying to build my project with Visual Studio 2015.
Description
I'm using MSBuild 14.0 and the 2015 compiler and encounter the following error :
fatal error C1060: compiler is out of heap space
quite randomly.
After that, random errors like the following will appear, but the one described upper is always the first one.
fatal error C1090: PDB API call failed, error code '24':
Internal Compiler Error in C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64_x86\CL.exe.
cl : Command line error D8040: error creating or communicating with child process
Using MSBuild 12.0 and the 2013 compiler on the same build worker image is running perfectly.
The visual 2013 & 2015 solutions are generated using gyp.
The project itself is on GitHub and is private, so I can't share here the code I'm using. But I don't think this is a big issue for the following reasons :
- It's C++ code, it is quite modern C++ but not heavily templatized
- I can reproduce the error on a local VM with interesting results described below
Findings
I can reproduce the problem on a local VM I have set up with Windows 10 and Visual 2015. If I set the VM memory to 4 GB (the same as the build worker image), then it will show the same behaviour.
Also I know it does not come from the C++ code itself, as I can run MSBuild several times and after some point (at most 3 consecutive builds) have my project correctly built and linked.
The behaviour upper is the same with update 1 or update 2 of MSVS2015.
I'm not using precompiled headers (this is what shows up mostly when searching for this error on google/stackoverflow)
Question
I'm quite surprised as it seems I'm the only one facing this error. But maybe others found a working and acceptable workaround for this problem?
Any information on that matter would be greatly appreciated.
Thanks,
Raphael
Hi,
I have a problem when trying to build my project with Visual Studio 2015.
Description
I'm using MSBuild 14.0 and the 2015 compiler and encounter the following error :
quite randomly.
After that, random errors like the following will appear, but the one described upper is always the first one.
Using MSBuild 12.0 and the 2013 compiler on the same build worker image is running perfectly.
The visual 2013 & 2015 solutions are generated using
gyp.The project itself is on GitHub and is private, so I can't share here the code I'm using. But I don't think this is a big issue for the following reasons :
Findings
I can reproduce the problem on a local VM I have set up with Windows 10 and Visual 2015. If I set the VM memory to 4 GB (the same as the build worker image), then it will show the same behaviour.
Also I know it does not come from the C++ code itself, as I can run MSBuild several times and after some point (at most 3 consecutive builds) have my project correctly built and linked.
The behaviour upper is the same with update 1 or update 2 of MSVS2015.
I'm not using precompiled headers (this is what shows up mostly when searching for this error on google/stackoverflow)
Question
I'm quite surprised as it seems I'm the only one facing this error. But maybe others found a working and acceptable workaround for this problem?
Any information on that matter would be greatly appreciated.
Thanks,
Raphael