Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Android Studio emulator cannot set up guest memory 'pc.ram': Invalid argument

I’m unable to launch an emulator in android studio due to the following error:

emulator: WARNING: Increasing RAM size to 1GB emulator: device fd:620 HAXM is working and emulator runs in fast virt mode Cannot set up guest memory 'pc.ram': Invalid argument

When installing HAXM I set the memory to 1024MB and the emulator (using Nexus 5) has been configured to only use 256MB of RAM :

I’ve tried increasing/decreasing the RAM setting but it appears to have no affect with the same error message appearing each time.

I don’t understanding why this is happening and have tried installing different versions of Android Studio. I’m currently running 1.3.2 which is the version my colleague is successfully using on the same spec PC (4GB ram, Windows 7 32 bit).

The error indicates that the emulator is trying to increase its RAM size to 1GB dispite it being set to 256MB.

like image 393
Stevezmac Avatar asked Oct 13 '15 10:10

Stevezmac


People also ask

How do I give my emulator more RAM?

Go to Tools->Android->AVD Manager , there's something like pencil to edit your AVD click on that, then in the pop-up window click Show Advanced Settings and there you can change the RAM size.

How much RAM do you need for AVD?

However, the heap size should not be less than 12 MB. o Depending on your computer specs, the recommended ram size is in the range between 512 MB – 1024 MB.

Can I run Android emulator with 8gb RAM?

2 GB RAM(DDR3/DDR4/DDR5) minimum, 8 GB RAM recommended. 2 GB of available disk space(HDD/SSD) minimum, 4 GB Recommended (500 MB for IDE + 1.5 GB for Android SDK and emulator system image)

How do I fix an emulator problem?

If the emulator fails to launch due to the error vulkan-1. dll cannot be found , you probably need to update the emulator. To update the emulator in Android Studio, go to Tools > SDK Manager and install the latest stable version of Android platform.


1 Answers

It appears that down grading the system image from Marshmallow (API 23) to KitKat (API 19) has resolved this issue. Its been stable for a week and the emulator isnt trying to increae the RAM size.

like image 161
Stevezmac Avatar answered Sep 27 '22 19:09

Stevezmac