Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build tf_core_kernels on With VS2015 stops with "fatal error C1060: compiler is out of heap space" #15393

Closed
stefanopiovesan opened this issue Dec 15, 2017 · 10 comments
Labels
stat:awaiting response Status - Awaiting response from author

Comments

@stefanopiovesan
Copy link

System information

  • Build tf_core_kernels.vcxproj
  • Windows 10 Enterprise Build 1607
  • TensorFlow installed from source
  • TensorFlow version Release 1.4.0 from github
  • VS2015 Enterprise 14.0.25431 Update 3

Cannot build tf_core_kernels.vcxproj (generated with CMake) because of a fatal error C1060: compiler is out of heap space.

Source code / logs

1>------ Build started: Project: tf_core_kernels, Configuration: RelWithDebInfo x64 ------
1> training_ops.cc
1>e:\software\tensorflow\tensorflow\contrib\cmake\build\external\eigen_archive\unsupported\eigen\cxx11\src/Tensor/TensorBase.h(245): fatal error C1060: compiler is out of heap space
1> INTERNAL COMPILER ERROR in 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\CL.exe'

@tensorflowbutler tensorflowbutler added the stat:awaiting response Status - Awaiting response from author label Dec 15, 2017
@tensorflowbutler
Copy link
Member

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

@spiovesan
Copy link

Have I written custom code: No
OS Platform and Distribution: Windows 10 Enterprise Build 1607
Bazel version: N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce:
Followed instructions here:
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/cmake
and then:
MSBuild /p:Configuration=RelWithDebInfo ALL_BUILD.vcxproj

@rongjiecomputer
Copy link
Contributor

I hit this out of heap space error before as well, this prones to happen when you don't have enough RAM.

A workaround is to remove all /MPcompile flag to make cl.exe create less processes and hence use less memory (works for me).

@snnn
Copy link
Contributor

snnn commented Dec 18, 2017

If may because of two things:

  1. you don't have enough memory.

  2. you are using 32 bits toolchains.
    Please upgrade cmake to 3.10.x and add "-T host=x64" to cmake command line args.

@tensorflowbutler
Copy link
Member

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue? Please update the label and/or status accordingly.

@spiovesan
Copy link

I compiled manually one file at a time and then it worked. But compiling the whole project is still an issue.

@tensorflowbutler
Copy link
Member

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

2 similar comments
@tensorflowbutler
Copy link
Member

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

@tensorflowbutler
Copy link
Member

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

@habom2310
Copy link

In the install instruction from tensorflow, it's already been mentioned.
Building TensorFlow from source can use a lot of RAM. If your system is memory-constrained, limit Bazel's RAM usage with: --local_resources 2048,.5,1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat:awaiting response Status - Awaiting response from author
Projects
None yet
Development

No branches or pull requests

6 participants