Just checking if anyone has come across this behavior. Should I open a bug at b.android.com? What information should I attach to help with the debugging?
On Friday, 24 April 2015 12:33:00 UTC+5:30, Kiran Rao wrote: > > I noticed a surprising behavior when starting the emulator on 64-bit > Linux: You need to have *both the x86 and x86-64 versions of the system > images installed *- otherwise the emulator never starts (CPU usage goes > to 100% with memory just hovering around 50-60MB) > > Is this working as intended? Is this documented somewhere? > > *OS: Fedora 20 64-bit* > > Steps to repro: > 1) Using SDK manager, install just the "*Intel x86 Atom_64 System Image*" > for a particular API version (say 22) > 2) Create an AVD using the AVD manager. In the "System Images" screen, > choose the on that shows "*22*" in the *API level* column and "*x86_64*" > in n the *ABI* column. > 3) Try starting this AVD > > At this point, the CPU usage for the emulator process goes up to 100% and > stays there. The memory usage is under 100MB and the emulator never starts. > > Steps to fix: > 4) Also download the "*Intel x86 System Image*" for the same API level > 5) While creating the AVD, choose the one that shows *x86* (NOT x86_64) > in the *ABI* column. > 6) Now go and start this AVD - everything works fine. > > One thing to note is that even though I created the AVD with x86 ABI, the > process that is run is still *emulator64-x86*, which is the same as > before. > > Regards, > Kiran Rao > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
