BUILD ISSUE: Compiling mediapipe/util/tracking/motion_estimation.cc failed #403
Comments
|
Can you confirm that OOM killer did not kill the process? |
|
I'm not 100% sure. My computer has 16 GB of memory and I gave the process 13 GB. Here's the command I ran: My CPU only has 4 cores so I gave it 2 as well. However, now that I think about it, my default swap space is pretty low (1GB) so I wonder if that matters. |
|
I think you have assigned too much memory. Rem If your CPU supports hyperthreading
docker run --cpus=6 --memory=6g ^
--mount type=bind,src=%CD%\Packages,dst=/home/mediapipe/Packages ^
--mount type=bind,src=%CD%\Assets,dst=/home/mediapipe/Assets ^
-it mediapipe_unity:linux |
|
That's interesting, I did not expect this issue. I'll try the solution and see what happens |
|
I retry running the docker container with this command: The reason why I didn't use 6 like yours is because my processor only has 4 cores. I also follow the formula here and even give it an extra 1GB:
The script runs fine and move past the previous error. However, it now stops at this point: Error Log
I didn't kill the process by any mean. There are no other process running at the same time as well so it wasn't a memory issue. Bazel's status code 37 refers to an Internal Error, which is not very helpful.. Some other research points to an issue with too many concurrent job running. A possible solution is reduce the number of concurrent jobs, which I don't know if I can do through Docker. Another is expanding memory, which caused a weird issue earlier. I'll retry again tomorrow with |
This is a typical error when the process is killed by an OOM killer (cf. bazelbuild/bazel#3020).
If your CPU supports hyperthreading (and if your CPU is made by Intel or AMD, it most likely does), I guess you can assign 6 to
|
|
Seems like I can't do that:
This is strange because my CPU does have hyper-threading: Here's the CPU info link if you want to double check. I'll retry with 4 GB of memory. Perhaps it does only need extra memory. |
|
I retried with 4GB of memory and the original error happened again. Besides that, there are these warnings too. They were also there in the original error. Warnings
There were quite a few of them and it's all Java files. |
|
Tried with 2GB, also didn't work. I was able to get a built version off a friend though so I think I'm good for now. |
|
I'll close this issue for now since I don't think I'll keep working on it |
homuler
added
docker
System information
Describe the problem
When I'm running the
build.py, the build failed around the 2899 step. The script ran into an exception and stopped.Guide I used: Windows Docker Linux Container. I followed all the steps as stated.
Command I ran that malfunctioned:
python build.py build --android arm64 -vv.Things I tried to fix:
Dockerfileas welll.Just the error
Steps to reproduce the issue
Provide the exact sequence of commands / steps that you executed before running into the problem.
git patch.python build.py build --android arm64 -vv, the command runs for about 20 mins then stopped and threw the error above.I couldn't retrieve all but hopefully these logs are enough.
Full logs
Additional context
Add any other context about the problem here.
I tried using the Ubuntu
Dockerfileas well but nothing changes. It threw the same error.EDIT: Move logs into collapsible content.
The text was updated successfully, but these errors were encountered: