Originally Posted by cdesai

type "which bash" and post the output



It means your pc does not have enough RAM available, and it ran out of free memory

but it does flow over to swap right? if ram is full??
i have 2.5gb ram and a 5gb swap disk... enough???

Sent from my X10i using XDA

Originally Posted by championswimmer

but it does flow over to swap right? if ram is full??
i have 2.5gb ram and a 5gb swap disk... enough???

Sent from my X10i using XDA

I have 3 gigs of ram and a 10 gig swap but I still got that error until I changed that and it worked.

Sent from my Transformer TF101 using Tapatalk 2

I've got 2g or ram and 5 of swap and have been able to compile successfully until I repo synced yesterday. Now it gets that memory error at the end as described. I'd successfully compiled just a few days ago though. I'll try the memory edit you mentioned and report back how it goes for me, cm9.

ok, i tried both 1024 as mentioned, and 512...

running:  mkbootimg --kernel /tmp/targetfiles-6OULAx/BOOT/kernel --cmdline console=ttyHSL0,115200,n8 --base 0x80400000 --ramdiskaddr 0x81800000 --ramdisk /tmp/tmpeRBouv --output /tmp/tmp7LjFIu
  running:  openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
  running:  java -Xmx512 -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpUajvDH out/target/product/ville/cm_ville-ota-eng.jhutson456.zip
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(Arrays.java:2786)
    at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
    at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161)
    at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
    at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:272)
    at com.android.signapk.SignApk.copyFiles(SignApk.java:422)
    at com.android.signapk.SignApk.main(SignApk.java:490)

   ERROR: signapk.jar failed: return code 1

make: *** [out/target/product/ville/cm_ville-ota-eng.jhutson456.zip] Error 1

is it possible to create that memory call as a variable? This way it could just grab whatever memory is available.

Just a thought but maybe you need to change it to 0512 . Im no expert but it may be looking for a 4 digit number.

Sent from my Transformer TF101 using Tapatalk 2

Originally Posted by lanternslight456

I've got 2g or ram and 5 of swap and have been able to compile successfully until I repo synced yesterday. Now it gets that memory error at the end as described. I'd successfully compiled just a few days ago though. I'll try the memory edit you mentioned and report back how it goes for me, cm9.

ok, i tried both 1024 as mentioned, and 512...

running:  mkbootimg --kernel /tmp/targetfiles-6OULAx/BOOT/kernel --cmdline console=ttyHSL0,115200,n8 --base 0x80400000 --ramdiskaddr 0x81800000 --ramdisk /tmp/tmpeRBouv --output /tmp/tmp7LjFIu
  running:  openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
  running:  java -Xmx512 -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpUajvDH out/target/product/ville/cm_ville-ota-eng.jhutson456.zip
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(Arrays.java:2786)
    at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
    at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161)
    at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
    at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:272)
    at com.android.signapk.SignApk.copyFiles(SignApk.java:422)
    at com.android.signapk.SignApk.main(SignApk.java:490)

   ERROR: signapk.jar failed: return code 1

make: *** [out/target/product/ville/cm_ville-ota-eng.jhutson456.zip] Error 1

is it possible to create that memory call as a variable? This way it could just grab whatever memory is available.

I'm having no luck either man. Here's a thread I started about the out of memory problem that I am having , http://forum.xda-developers.com/show....php?t=1682722. I have tried everything I could find on the internet to fix it but every time I try and build cm it just fails as out of memory towards the end. The funny thing is I can build AOSP just fine and fast. I'm at a complete loss.

Sent from my GT-N7000 or Galaxy Nexus

It's so frustrating because I was able to compile it just a few days ago. Then I did a repo sync, it updated some things, and I'm hosed...

Sent from AndroidInsomnia H.Q.

Originally Posted by Dreamboxuser

As for the ram I found this on another tutorial here http://rootzwiki.com/index.php?/topic/18318-[TUTORIAL]-How-to-Compile-Gummy-for-Non-Moto-Devices#entry482777


Again not my work but it worked for me. Probably have to change gummy to whatever you are using.

Sent from my TF101 using Tapatalk 2

It works for any build I've had to do it for gummy, evervolv, and a couple of others and if it doesn't work try 512 instead of 1024. It should be line 374 in common.py

Sent from my DROID BIONIC using Tapatalk 2

Originally Posted by Dreamboxuser

Just a thought but maybe you need to change it to 0512 . Im no expert but it may be looking for a 4 digit number.

Sent from my Transformer TF101 using Tapatalk 2

I don't think so. It is just looking for specific amounts of RAM and they will always be 256, 512, 1024 etc I've had 512 and it worked fine

Sent from my DROID BIONIC using Tapatalk 2

I've tried 1024, 512, and 256 with no luck. I have 2 gigs ram and 2 gigs swap. I even made sure that the terminal was the only thing open after a reboot... Still. The same memory fail.

Sent from AndroidInsomnia H.Q.

Originally Posted by lanternslight456

I've tried 1024, 512, and 256 with no luck. I have 2 gigs ram and 2 gigs swap. I even made sure that the terminal was the only thing open after a reboot... Still. The same memory fail.

Sent from AndroidInsomnia H.Q.

Java is iffy. It also don't care about your swap. It binds to the physical ram when its allocated. Lowering this below 1Gig isn't suggested. ICS needs at least a gig of VMheap for the emulator. 512 was cutting it close in GB. If you want to compile, add more ram. Its that simple. You might be able to get away with it by doing either one of two things.

1. Installing a slimmer desktop. (XFCE, LXDE)
2. installing another distro as a dual boot with no gui.

Have fun.