0

I'm been trying to build LinageOS 18.1 but keep running into OutOfMemoryError : Java Heap Space

I've increased the heap size with -Xxm25g and I can confirm it with java -version that the new heap size is indeed picked up by java, which shows Picked up _JAVA_OPTIONS: -Xxm25g

I've also setup a /swapfile size of 40GB

I have an 8GB RAM iMac with Ubuntu 18.04.6 on VMWare Fusion, using 4 processor

No matter how much -Xxm size I increase(even tried -Xxm50g), it still always errors out at this point of the build process :

//frameworks/base:api-stubs-docs-non-updatable metalava merged [common]

OutOfMemoryError : Java Heap Space

Is there a way to tweak the build process somewhere to get it to build?

I've read elsewhere that reducing the processor might also help, so I've also tried to reduce the no. processor to just 1 with brunch -j1 <target_name> but that doesn't work either as I believe Lineage uses the full available {n proc} so it's no accepting the -j argument. Is there a way to tell brunch to use just 1 processor?

I know an 8GB RAM is not the ideal build setup but I've read elsewhere it's possible. Thanks for any pointers help

Here's the memory statistics right before, during and after the failure :

dev@ubuntu:~$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.4G        3.9G        2.5G        5.1M        1.0G        3.2G
Swap:           49G        495M         49G
dev@ubuntu:~$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.4G        3.9G        2.4G        5.1M        1.0G        3.2G
Swap:           49G        495M         49G
dev@ubuntu:~$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.4G        4.2G        2.0G        5.1M        1.2G        3.0G
Swap:           49G        495M         49G
dev@ubuntu:~$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.4G        4.2G        2.0G        5.1M        1.2G        2.9G
Swap:           49G        495M         49G
dev@ubuntu:~$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.4G        4.4G        1.6G        5.1M        1.4G        2.7G
Swap:           49G        495M         49G
joke4me
  • 812
  • 1
  • 10
  • 29
  • 1
    From the memory statistics we can infer the error is not the physical/vm memory issue, rather in the Java JVM itself, or rather the build script may have to be adjusted – joke4me Sep 21 '22 at 16:09

0 Answers0