tensorflow-on-raspberry-pi icon indicating copy to clipboard operation
tensorflow-on-raspberry-pi copied to clipboard
verified publisher icon samjabrahams

have heap problem with running ./compile.sh in bazel step

Open fevemania opened this issue 8 years ago • 3 comments

Describe the Issue

I have already revise both "scripts/bootstrap/compile.sh" and "tools/cpp/cc_configure.bzl", but it seems I get some problem with heap.

Is that have any to do with bazel 0.4.3 ? (I currently try 0.4.3) 2017-04-11 09 42 49

Steps to Reproduce

Followed step by step installation by source, final step is ./compile.sh in bazel folder

Hardware/Software Info

Please provide the following information about your Raspberry Pi setup:

  • Raspberry Pi model: Raspberry Pi 3 Model B
  • Operating System used: Raspian - NOOBs installation -- debian_version : 9.0
  • Version of Python used: python3.5
  • SD card memory size: 32GB
  • Size of USB/other device used as swap (if building from source): 16GB
  • TensorFlow git commit hash (if building from source):

Relevant Console Output/Logs

2017-04-11 09 39 30

compile time: around 3-4 hours (from initial bazel to get error)

fevemania avatar Apr 11 '17 09:04 fevemania

Hi @fevemania - thanks for opening this up. Let's try a few things:

  • First, you should use Bazel 0.4.5 instead of 0.4.3 (you'll run into an error once you get to the TensorFlow stage). It looks like I screwed up and forgot to update this step in the GUIDE- I just pushed a new url in the relevant build step. Sorry for wasting your time with that.
  • Second, let's make sure that your swap drive is properly setup. Could you copy/paste the result of running free in the terminal?

samjabrahams avatar Apr 11 '17 19:04 samjabrahams

Thanks for reply @samjabrahams

Sorry for late. This week I have the midterm exam, and just finish it today.

I just redo every step till compile.sh

This time I use bazel 0.4.5 before start compile, I have the snapshot about swap 2017-04-13 16 10 08 2017-04-13 16 12 11

I also do manual clear memory before compile: 2017-04-13 16 21 18

This photo is in running time: 2017-04-13 20 55 29

but after 5 hours, it still fail. 2017-04-13 22 09 29

fevemania avatar Apr 13 '17 14:04 fevemania

Sorry for the delay- I've been out and about. Let's try switching back to Oracle JDK instead of OpenJDK:

Actually- let's try switching back to the Oracle JDK instead of OpenJDK.

sudo update-alternatives --config java

Select the option for Oracle JDK 8 and see if that works any better.

samjabrahams avatar Apr 30 '17 19:04 samjabrahams