So, like a lot of people starting Android development with Eclipse, even with a fast machine, I notice that the emulator runs frustratingly slow.
I search SO for any tips to make it run faster and I run across this question, whose top answer suggests a couple of things, including making the AVD have more RAM. They suggest 1024MB:
Sounds good. But when I try to launch it, I get this:
Failed to allocate memory: 8 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
If I set it to 512MB (up from the default 256MB) it launches fine.
But why, on a Windows 7 x64 machine with 12GB of physical RAM can I not allocate 1024MB to an AVD? Is it an Eclipse limitation? Emulator limitation? Java limitation? I presume the person in that other question got it working but I’ve yet to figure out how and most of the responses I see elsewhere say “yeah dial it down to 512MB” which is not the answer I’m looking for.
From Galaxy s3 emulator:
There is a common problem when setting up the AVD that you have to manually edit the config file to fix. File is located at
C:\Documents and Settings\username\.android\avd\name_of_avd.avd\config.ini
Change the memory settings from
(Do not enable word wrap in notepad).
Save the file and reopen the avd.
This worked for me.
Weird, but this worked for me on Windows 7 x64 machine with 16GB of RAM. You do have to add MB at the end of “hw.ramSize” in config.ini.
I had the same problem like OP wrote. Also, if you need 2 gigabytes of RAM, write 2048MB and simulator will run from Eclipse.
I have the same problem occasionally, and I’m unable to tell you exactly why this problem occurs, but it seems that the AVD won’t start if it has been allocated more then an X percentage of your available RAM at the time of starting.
If you lower the given amount by just 50mb, you’ll often notice it will run just fine. Or, similarly, if you close a few programs to save some RAM, it will also boot up perfectly fine.
I know it’s not ideal, but I suggest to just lower the allocated RAM in small amounts until it boots up. I wish I could give a better answer but I haven’t been able to find a reason myself either.
Try starting the AVD without Eclipse to remove that Factor.
This can be done by navigating to your SDK-Path/tools and open Android(.bat?) and then select the AVD manager.
I would recommend opening a command shell, navigating to the path and then run
emulator -avd AVDNAME -scale 0.7 -no-boot-anim
You can also try starting it without the scale parameter or maybe even a lower number.
On Windows, emulating RAM greater than 768 may fail depending on the system load
- Open C:\Users\your user.android\avd\yourAVD.avd\config.ini
this worked for me 🙂
hope it will help!