Emulator increases the amount of RAM by itself [367746301]

Fixed

Bug

Status Update

No update yet.

Description

ma...@paramount.com

created issue #1

Sep 18, 2024 07:40AM

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

Create an Android TV device say with API 31 arm and RAM 1024 MB
Start the emulator

Expected: The emulated device has 1024 MB of RAM

Actual: The emulated device has 2048 MB of RAM

The issue is simple - emulator increases the RAM to whatever is required, but the GUI does not check for it so it allows you to set whatever value.

ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE

ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac) The related output is INFO Increasing RAM size to 2048 MB

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: all Version of Gradle Plugin: n/a Version of Gradle: n/a Version of Java: n/a OS: MacOS Sonoma n/a

Comments

rk...@google.com <rk...@google.com> Sep 18, 2024 03:01PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> #2Sep 18, 2024 06:38PM

Reassigned to jp...@google.com.

Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.

jp...@google.com <jp...@google.com> #3Sep 18, 2024 06:51PM

Reassigned to sn...@google.com.

Thanks for the report. I believe that this is fixed in our development branch, and also in the branch that will become Ladybug Feature Drop Beta. If you could verify that this doesn't happen in a nightly build (from https://developer.android.com/studio/nightly) that would be helpful -- and of course if you can trigger this in a recent nightly build, that's would be very important information.

sn...@google.com <sn...@google.com> #4Oct 8, 2024 11:23AM

Reassigned to jp...@google.com.

Sorry, I have not tried it on the nightly build, but since then I updated to Meerkat and I have not seen the freeze afterwards.

jp...@google.com <jp...@google.com> #5Oct 9, 2024 10:58PM

Marked as fixed.

That's good to hear. I think that the fix (which for reference was https://github.com/JetBrains/intellij-community/commit/fe621544dd61a9af34d97958d3d823a7c3454a87) is effective for both beta and canary branches.

For the record I am also arranging for https://github.com/JetBrains/intellij-community/commit/a444c8a500883669fc05c7177f93b5b794fdd13b (same fix, different implementation class) to be included; it's probably inactive code in our configurations, but it might be possible to trigger nevertheless.

Thanks for the confirmation!

Issue 367746301