This week's book giveaway is in the Go forum.
We're giving away four copies of Head First Go and have Jay McGavren on-line!
See this thread for details.
Win a copy of Head First Go this week in the Go forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
Bartenders:
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

Emulator qemu_ram-alloc_user_backed: call  RSS feed

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

When I run my app on emulator (tried Galaxy Nexus API 26 and Nexus 4 API 28), in both cases got same outcome in Event Log:
10:44 Emulator: qemu_ram_alloc_user_backed: call

at the same time Gradle build is finished with no issues and project is synched successfully.
I got this problem anytime I launch one particular app - I wonder if it is a problem with ram in general on the computer I use or this single app takes too much from my resources.

I use:
Android Studio: 3.4 Beta 5
Gradle Version: 5.1.1 (Plugin Version : 3.4.0-beta05)
JRE: 1.8.0_152


Because I got purple moose badge I will not add more reflections.

BRGDS,
Z.
 
Saloon Keeper
Posts: 20514
115
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm not sure what a "purple moose badge" is (purple moosage?), or why it would make you reticent, but that's OK. I checked your profile and nobody has anything bad to say about you.

The qemu system is a virtual machine manager. Unlike many other VMs, however, it can manage not only VMs for the native hardware of the computer you are actually running on, but also emulated CPUs. In the case of your Android devices, that's probably some sort of ARM CPU. You can, incidentally, also emulate the ARM CPU used by the Raspberry Pi and run a virtual Pi on your desktop, although that's not important here. Just interesting.

Definitely check to see if your development machine has enough available RAM by launching a system monitor app such as Windows Task Manager or (for Linux and MacOS) the "top" utility. If you have enough ram, check your development preferences to make sure that the emulated machine has been allocated enough RAM. Offhand, I don't know where to find those, but they're probably there somewhere.

If you have enough available RAM, then it's possible that you have a defective version of qemu and need to upgrade it. It's probably bundled with Android Studio, so you might have to download and run a newer (or sometimes older) version. One that doesn't have that bug, in other words.
 
Zuzanna Rosin
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Tim,
 
Tim Holloway
Saloon Keeper
Posts: 20514
115
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

as I am recently stuck with my emulator I would like to extend my doubt regarding the "best solution" in my case.
As my emulatordoes not work with the JDK I used (I used JRE 1.8.0_181) I switched to JDK 11.0.1 and tried running the app with it.
Unfortunately I ended with the same error (Emulator qemu_ram-alloc_user_backed: call). I looked for this error in available forums, as much as I did I find no optimal solution, so further doubts consider uninstalling AS and Java at all and installing everything all over again. But here comes my question; should I do this or should I rather wait for another AS update, hoping that the bug after reporting should be fixed.



The qemu emulator is not written in Java, so changing your JVM version would not help. You need a different version of qemu itself. Which means that you need to try a different version of Android Studio or get AS to update its qemu component, if that's a supported option.
 
Zuzanna Rosin
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim,

Is it really a point downgrading As? I use recent release. I wonder if the problem might be connected with the fact I work on notebook with two monitors. May it be a CPU problem which is not detected by Task Manager?
 
Tim Holloway
Saloon Keeper
Posts: 20514
115
Android Eclipse IDE Linux
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Don't over-complicate things. The Android VM does not use any of your native hardware. It has a completely different CPU and completely different peripherals. If there was a problem with your actual development computer, it's very, very unlikely that it would only show up in qemu.

Sometimes the latest and greatest version of software isn't so great. I've had to roll back products that we paid what would probably be about $15,000 a month for because they had fatal flaws. We waited until an even later version came out, then resumed our normal roll-forward (upgrade) process, skipping the defective release entirely.
 
Zuzanna Rosin
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I decided to continue the thread regarding qemu, because
after AS upgrade to 3.5 Canary 7, I uninstalled and installed Emulator package in SDK Tools,
still I have this repeating error:

09:51 Executing tasks: [:app:assembleDebug]

09:52 Gradle build finished in 58 s 326 ms

09:52 Emulator: qemu_ram_alloc_user_backed: call




Connected to process 5663 on device 'Pixel_3_Edited_ListView_API_28 [emulator-5554]'.
Application terminated.
 
Tim Holloway
Saloon Keeper
Posts: 20514
115
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have you looked at this: https://developer.android.com/studio/run/emulator-troubleshooting ?
 
Zuzanna Rosin
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
NOW I can say I did it by heart, thank you.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!